# Accessibility Statement This is the Markdown copy of [Accessibility Statement](https://nash.com.ph/accessibility), published by NASH Reviewer, an independent practice platform not affiliated with DepEd, BHROD, or NEAP. Our commitment to an accessible NASH Reviewer, the standard we work to, how we test, what does not work well yet, and how to tell us about a barrier. *Effective & last updated: November 13, 2026* ## Our Commitment NASH Reviewer is for every teacher and aspiring school head, including those who use a screen reader, a keyboard instead of a mouse, larger text, a high-contrast theme, or a phone held in one hand. We want the practice sets, the guides, the data pages, and the blog to work for all of them. Accessibility is part of how each page is designed, built, and checked before it is published. It is not a separate version of the site, and it is not a step left for later. This statement covers nash.com.ph, including [the blog](https://nash.com.ph/blog). ## The Standard and Where We Stand Our goal is the [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/) at Level AA, the international standard for accessible websites. NASH Reviewer is **partially conformant** with WCAG 2.2 Level AA. Partially conformant means that most of the site meets the standard and some parts do not yet; those parts are listed under [Known Limitations](https://nash.com.ph/accessibility#limitations). This is our own assessment. No outside auditor has reviewed the site. We also follow Google Chrome’s [Modern Web Guidance](https://github.com/GoogleChrome/modern-web-guidance), a set of current practices for accessible HTML, forms, color, and motion, and the WAI-ARIA patterns for controls such as tabs and dialogs. ## What We Build Into Every Page - **Structure:** Every page has one main heading, headings in order, named navigation areas, and real lists and tables, so a screen reader can move through a page the way the eye does. A “Skip to content” link is the first stop on every page. - **Keyboard:** Every link, button, field, menu, and practice question works with a keyboard alone, and the item in focus always shows an outline. On the practice platform, focus moves to the main heading of each new page. Menus and dialogs close with the Escape key and return you to where you were. - **Text size:** Pages follow the text size set in your browser or device. At 200% text on a phone, every public page still fits the screen without scrolling sideways. - **Color and contrast:** We design text to a contrast of at least 4.5 to 1 against its background, and the outlines of form fields to at least 3 to 1, in both the light and the dark theme. Nothing is shown by color alone: a result, an error, or a selected choice is also stated in words or drawn as a shape. Windows contrast themes are supported. - **Touch:** Buttons, menu items, links in lists, and form fields are at least 44 pixels tall on touch screens. - **Motion:** Animation is brief and is removed when your device asks for reduced motion, with one exception: the drawing at the top of the blog’s home page plays a sample practice item on its own while it is on screen. It pauses when you scroll past it, has a Pause button, and stays still, showing the scored answer, when your device asks for reduced motion. Videos and the interactive diagrams in blog posts start only when you press Play. - **Forms:** Every field has a visible label, with instructions above the field. An error is written in words next to its field and announced to screen readers, and each form says which fields are required. - **Images and charts:** Images that carry information have a text description. A chart’s figures are also given as text, as a table, or as a file to download. - **Language:** Each page declares its language, and Filipino passages on the blog are marked so that a screen reader pronounces them as Filipino. ## How We Test We check accessibility whenever we change a page, a component, or a style, not once a year: - **Automated checks on every public page:** axe-core, an open-source accessibility testing engine, runs the WCAG 2.2 Level A and AA rules on every public page of the practice platform and the blog, on a phone-size screen, in the light and the dark theme. A page that fails is fixed before the change is published. - **Large text:** Every public page is loaded at 200% text on a phone-size screen and must not scroll sideways. - **Structure:** Every public page is checked for one main heading, headings in order, and named navigation areas. - **By hand:** We use each new control with a keyboard alone, in both themes, at phone and desktop sizes, and with a high-contrast theme simulated in the browser. - **Full reviews:** In November 2026 we reviewed the whole practice platform and the blog against the Modern Web Guidance on accessibility, HTML, forms, color, and motion. Each problem found was confirmed in a browser and then fixed. Automated checks find only part of what matters. Our testing does not yet include: - regular testing with screen readers such as NVDA, JAWS, VoiceOver, and TalkBack; - testing by people with disabilities; and - a review by an independent accessibility auditor. ## Browsers and Assistive Technology - NASH Reviewer is built with standard HTML, CSS, and JavaScript, with WAI-ARIA where a control needs it, and relies on them to work with assistive technology. - It is made for the current versions of Chrome, Edge, Firefox, and Safari on Android, iOS, Windows, and macOS. Older browsers may not show every page correctly. - The guides and the blog can be read with JavaScript turned off. Practice sets, sign-in, and search need it. - The site follows your device’s settings for text size, light or dark colors, reduced motion, and contrast themes. ## Known Limitations These parts of the site do not fully meet the standard yet. For each, we say what you can use instead: - **Timed practice questions:** Each practice question has a time limit, because the practice follows the timed format of the NASH. The limit cannot be extended or turned off yet. The timer stops once you answer, explanations and results are not timed, and you can pause between questions. - **Sign-in and account screens:** These come from our sign-in provider. We can adjust how they look, but not everything about how they work with assistive technology. - **Charts:** The small labels along a chart’s axes do not grow with your text size. The chart’s figures are given with it as text or as a table. - **Documents from DepEd and other agencies:** The manuals, orders, and templates in the blog’s Resources are shared as their publishers issued them. Many are scanned pages without the tags or text a screen reader needs. Each resource’s page describes what its document contains. - **Our PDF copies:** The PDF copies of our practice sets are made for printing. The same sets on their web pages are the accessible version. - **Videos:** Videos on the blog play from their publishers’ channels, so their captions depend on the publisher. Each video’s title and a summary are written on the page. - **Maps and interactive diagrams:** The school map and the blog’s interactive diagrams are visual. The facts they show are also given as text on the same page. The animated drawing on the blog’s home page is described in one passage of text for screen readers. - **Screen readers:** We do not yet test with screen readers routinely, so some controls may be announced less clearly than we intend. If one of these keeps you from using NASH Reviewer, [tell us](https://nash.com.ph/accessibility#feedback) and we will help you another way. ## Tell Us About a Barrier If any part of NASH Reviewer does not work for you, please tell us. Use our [contact page](https://nash.com.ph/contact), or email [support@nash.com.ph](mailto:support@nash.com.ph?subject=Accessibility) with “Accessibility” in the subject. It helps us to know: - the address of the page; - what you were trying to do, and what happened; and - your device and browser, and any assistive technology you use, such as a screen reader or a magnifier. We read every report and reply by email. We will tell you what we found and what we will change. If you need something on the site in another form in the meantime, say so and we will send it to you another way. ## About This Statement This statement was prepared on November 12, 2026 from our own testing, described above. We update it when the site or our testing changes, and we review it at least once a year. ## Contact Us Send accessibility reports and questions to: Edventure Web Development Services, doing business as “NASH Assessment” and “NASH Reviewer” Zone 1, Katipunan Street, Brgy. Lawa-an (Pob.) Basey, Samar 6720, Philippines support@nash.com.ph 0926 021 1602