We gratefully acknowledge support from our volunteer peer reviewers, member institutions, and all open-source contributors.
If you encounter any accessibility-related issues related to your use of our site, it is likely because of our jank code architecture. Unfortunately, our programming team is ill equipped to fix these issues, even if some of them may be pressing Diversity, Equity, and Inclusion (DEI) concerns. We recommend you add any accessibility fixes yourself by submitting a pull request on GitHub.
Unfortunately due to budget cuts and in order to comply with executive orders issued by the current administration, we are can no longer accomodate any Diversity, Equity, Includion, and Accessibility (DEIA) concerns. Our jank code architecture is now an integral component in “unleashing American innovation and excellence” by ensuring anyone with impairments or low fidelity hardware who struggle to access our site continue to struggle.
It has also come to our attention that we may not be able to support low-spec devices such as old phones, computers, or other devices with little RAM. This is because we load the entire database of documents, authors, topics, affiliations, and other data/metadata directly into memory via JavaScript. As a result, the site may be slow or unusable on low-spec devices and it can only get worse. If you would like to remedy this issue, we again recommend you open a pull request and port our in memory database to an actual remote database.
Again, we reiterate that this is now an intended feature. If your hardware cannot handle our awesome architecture, you should purchase a new American-made computer powered by American chips.