Accessibility testing

Braillia Accessibility Scan Report.

A readable view of the automated accessibility scan across Braillia pages, light and dark themes, desktop, mobile, and 320 pixel reflow layouts.

Markdown ReportJSON ReportProxy MarkdownProxy JSON

Routes

11

Viewports

3

Themes

2

Checks

66

Axe WCAG checks

Axe scans for automated accessibility issues tied to WCAG tags, including labels, color contrast, landmarks, headings, ARIA usage, forms, links, and keyboard-related structure.

Braillia custom checks

Braillia adds project-specific checks for one H1 per page, main landmarks, image alt text, accessible names on visible controls, page titles, and horizontal overflow.

Real page states

Each route is checked in light mode, dark mode, desktop width, mobile width, and 320 pixel reflow so layout and contrast problems are easier to catch.

ACR evidence preparation view

This section organizes scan evidence in a procurement-friendly format. It connects automated findings to WCAG, Revised Section 508, and EN 301 549 references, then separates sections verified by automated evidence from items that still need human assistive-technology review and certification.

Scan coverage

Base URL
http://localhost:3000
Viewports
desktop, mobile, reflow-320
Themes
light, dark

Screen-reader proxy evidence

This layer inspects the browser accessibility tree that assistive technologies rely on. It checks exposed landmarks, heading names, named controls, header navigation, Web Assist controls, and the Begin Page Reading start point.

Routes checked
11
Landmarks exposed
55
Headings exposed
243
Web Assist start
Braillia start page

Proxy report generated: May 11, 2026, 12:27 PM

Accessibility rule areas tested by the Braillia scan
Rule areaTest elementWCAG / 508 fitResult
Page titleDocument title
  • WCAG 2.4.2 Page Titled
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.2.4.2
Clear
Page landmarksMain landmark
  • WCAG 1.3.1 Info and Relationships
  • WCAG 2.4.1 Bypass Blocks
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.3.1
  • EN 301 549 9.2.4.1
Clear
HeadingsVisible H1 structure
  • WCAG 1.3.1 Info and Relationships
  • WCAG 2.4.6 Headings and Labels
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.3.1
  • EN 301 549 9.2.4.6
Clear
Image alternativesImage alt attributes
  • WCAG 1.1.1 Non-text Content
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.1.1
Clear
Control namesVisible links, buttons, and form controls
  • WCAG 2.4.6 Headings and Labels
  • WCAG 4.1.2 Name, Role, Value
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.2.4.6
  • EN 301 549 9.4.1.2
Clear
Responsive reflowHorizontal page overflow at tested viewport widths
  • WCAG 1.4.10 Reflow
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.4.10
Clear
Color contrastText and background contrast detected by Axe
  • WCAG 1.4.3 Contrast (Minimum)
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.4.3
Clear
ARIA and semantic structureARIA attributes, roles, labels, IDs, and semantic relationships detected by Axe
  • WCAG 1.3.1 Info and Relationships
  • WCAG 4.1.2 Name, Role, Value
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.3.1
  • EN 301 549 9.4.1.2
Clear
Keyboard and focus supportFocusable controls, visible names, navigation structure, and interactive element rules
  • WCAG 2.1.1 Keyboard
  • WCAG 2.1.2 No Keyboard Trap
  • WCAG 2.4.3 Focus Order
  • WCAG 2.4.7 Focus Visible
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.2.1.1
  • EN 301 549 9.2.1.2
  • EN 301 549 9.2.4.3
  • EN 301 549 9.2.4.7
Clear
ACR evidence preparation table with criteria, standards, evidence status, and remarks
CriteriaWCAG / 508 / EN 301 549Evidence statusRemarks and evidence

WCAG 2.4.2 Page Titled

Document title

  • WCAG 2.4.2 Page Titled
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.2.4.2
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for page title.

WCAG 1.3.1 Info and Relationships

Main landmark

  • WCAG 1.3.1 Info and Relationships
  • WCAG 2.4.1 Bypass Blocks
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.3.1
  • EN 301 549 9.2.4.1
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for page landmarks.

WCAG 1.3.1 Info and Relationships

Visible H1 structure

  • WCAG 1.3.1 Info and Relationships
  • WCAG 2.4.6 Headings and Labels
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.3.1
  • EN 301 549 9.2.4.6
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for headings.

WCAG 1.1.1 Non-text Content

Image alt attributes

  • WCAG 1.1.1 Non-text Content
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.1.1
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for image alternatives.

WCAG 2.4.6 Headings and Labels

Visible links, buttons, and form controls

  • WCAG 2.4.6 Headings and Labels
  • WCAG 4.1.2 Name, Role, Value
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.2.4.6
  • EN 301 549 9.4.1.2
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for control names.

WCAG 1.4.10 Reflow

Horizontal page overflow at tested viewport widths

  • WCAG 1.4.10 Reflow
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.4.10
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for responsive reflow.

WCAG 1.4.3 Contrast (Minimum)

Text and background contrast detected by Axe

  • WCAG 1.4.3 Contrast (Minimum)
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.4.3
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for color contrast.

WCAG 1.3.1 Info and Relationships

ARIA attributes, roles, labels, IDs, and semantic relationships detected by Axe

  • WCAG 1.3.1 Info and Relationships
  • WCAG 4.1.2 Name, Role, Value
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.1.3.1
  • EN 301 549 9.4.1.2
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for aria and semantic structure.

WCAG 2.1.1 Keyboard

Focusable controls, visible names, navigation structure, and interactive element rules

  • WCAG 2.1.1 Keyboard
  • WCAG 2.1.2 No Keyboard Trap
  • WCAG 2.4.3 Focus Order
  • WCAG 2.4.7 Focus Visible
  • Section 508 E205.4 via WCAG A/AA
  • EN 301 549 9.2.1.1
  • EN 301 549 9.2.1.2
  • EN 301 549 9.2.4.3
  • EN 301 549 9.2.4.7
Automated Verified

Automated testing across scanned routes, themes, and viewport states found no known issues for keyboard and focus support.

WCAG 1.3.2 Meaningful Sequence

Reading order across responsive layouts and assistive technology flows

  • WCAG 2.1 A
  • Section 508 E205.4
  • EN 301 549 9.1.3.2
Manual Review

Automation can identify structure signals, but final evidence should include manual keyboard and screen reader review.

WCAG 2.4.4 Link Purpose

Link text and surrounding context

  • WCAG 2.1 A
  • Section 508 E205.4
  • EN 301 549 9.2.4.4
Manual Review

Automated checks verify accessible names exist; manual review should confirm each link purpose is understandable in context.

WCAG 3.3.2 Labels or Instructions

Forms, contact fields, error-prevention guidance, and instructions

  • WCAG 2.1 A
  • Section 508 E205.4
  • EN 301 549 9.3.3.2
Manual Review

Automated checks can verify labels exist; manual review should confirm labels and instructions are clear enough for completion.

Screen reader usability review

VoiceOver, NVDA, or comparable assistive technology walkthrough

  • WCAG supporting evaluation
  • Section 508 functional performance review
  • EN 301 549 functional performance review
Manual Review

Procurement-grade reporting should include assisted manual review of navigation, menu behavior, modal behavior, and content comprehension.

Assistive technology proxy

Accessibility tree by page.

Clear
/46 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: Accessibility is not a checkbox. It is independence, dignity, and safety.
  • H2: From document delivery to real understanding.
  • H2: More than accessibility tools. A trusted connection to the information that matters most.
  • H2: Useful answers from the information in front of the user.
  • H2: Accessibility delivery without rebuilding every system.
  • H2: The outcome is not another file. It is usable access.
  • H2: Built for many document-heavy organizations.
  • H2: Clear answers for accessibility teams.
  • H2: Start with the information people cannot afford to miss.
  • H1: Blind and low-vision users should not have to wait for critical information.
  • H3: Real life does not wait for remediation.
  • H3: Accessibility only matters if people can actually use the information.
  • H3: Compliance is just the beginning.
  • H3: Deliver important information instantly
  • H3: Transform information into usable access
  • H3: Guide users directly to the information
  • H3: Help users act independently
  • H3: Braillia Options
  • H3: Scan Code
  • H3: Braillia Documents
  • H3: Document Reader
  • H3: Braillia Personal Assistant
  • H3: Braillia Messages
  • H3: Ask the document
  • H3: Find what matters
  • H3: Support next steps
  • H3: Connected systems
  • H3: Company Admin
  • H3: Portal delivery
  • H3: Faster access
  • H3: Cleaner handoff
  • H3: Better continuity
  • H3: More clarity
  • H3: Less support friction
  • H3: Program visibility
  • H3: Utilities
  • H3: Healthcare
  • H3: Government
  • H3: Insurance
  • H3: Financial services
  • H3: Education
  • H3: Telecommunications
  • H3: Transportation
  • H3: Housing
  • H3: Retail and daily life
  • H3: Legal and civic services
/accessibility-scan-report18 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: ACR evidence preparation view
  • H2: Scan coverage
  • H2: Screen-reader proxy evidence
  • H2: Accessibility tree by page.
  • H2: Results by page.
  • H2: Manual Verification Queue.
  • H2: Every scanned state.
  • H1: Braillia Accessibility Scan Report.
  • H2: Axe WCAG checks
  • H2: Braillia custom checks
  • H2: Real page states
  • H3: Hero image alt text quality
  • H3: Responsive reading order
  • H3: Link purpose clarity
  • H3: Web Assist modal flow
  • H3: Mega menu keyboard flow
  • H3: Contact form labels and instructions
  • H3: Screen reader walkthrough
/accessibility-compliance18 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: The standard names the principles. Braillia focuses on the user outcome.
  • H2: Clear answers for accessibility teams.
  • H1: Compliance should lead to usable outcomes.
  • H2: Braillia helps blind and low-vision users receive, understand, and act on critical information through accessible mobile experiences.
  • H2: Braillia focuses on information users can perceive, navigate, understand, and return to when it matters.
  • H2: Braillia provides a mobile path to document information through delivery, messages, QR pickup, and document-grounded Braillia AI support.
  • H2: Braillia can sit beside remediation, validation, and accessibility teams as the usable-access outcome layer.
  • H3: Perceivable
  • H3: Operable
  • H3: Understandable
  • H3: Robust
  • H2: Accessibility becomes meaningful when users can act on the information.
  • H2: Compliance explains the requirement. Usability proves the outcome.
  • H2: Reference points
  • H2: Start with a high-impact document pilot.
  • H3: Receive
  • H3: Understand
  • H3: Act
/accessibility-compliance-vs-usability40 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: The evolution is from technical conformance to real-world usability.
  • H2: Usability is what people actually experience.
  • H3: Can users actually receive, understand, navigate, and act on the information independently when it matters most?
  • H2: Braillia extends accessibility beyond static remediation.
  • H2: Braillia focuses on real-world accessible delivery.
  • H2: Braillia supports standards while extending accessibility into usable experiences.
  • H2: The future of accessibility is usable participation.
  • H2: Clear answers for accessibility teams.
  • H1: Accessibility compliance matters. Real accessibility is measured by usability.
  • H3: Tags matter
  • H3: Alt text matters
  • H3: WCAG matters
  • H3: Section 508 matters
  • H3: ADA programs matter
  • H3: Validation matters
  • H3: Can the user find the deadline?
  • H3: Can the user understand the instruction?
  • H3: Can the user ask what something means?
  • H3: Can the user know what action to take?
  • H3: Can the user do it without waiting on someone else?
  • H3: Easy to receive
  • H3: Easy to navigate
  • H3: Easy to understand
  • H3: Easy to ask questions about
  • H3: Easy to organize
  • H3: Easy to act on
  • H3: Available when the user needs it
  • H3: Receive
  • H3: Understand
  • H3: Act
  • H3: WCAG principles
  • H3: ADA accessibility initiatives
  • H3: Section 508 accessibility programs
  • H3: PDF accessibility workflows
  • H3: Assistive technology compatibility
  • H3: Screen-reader accessibility
  • H3: Structured navigation
  • H3: Semantic accessibility
  • H2: A document can pass accessibility checks and still fail the user.
  • H2: Start with a high-impact document pilot.
/accessibility-delivery-platform36 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: Organizations should not have to build this complexity themselves.
  • H2: AI assistance woven through the system and app.
  • H2: Built for organizations of every size.
  • H2: Centralized administration for accessible delivery at scale.
  • H2: Designed for organizations handling sensitive information.
  • H2: More than document processing. A complete accessibility delivery ecosystem.
  • H2: Clear answers for accessibility teams.
  • H1: The accessibility engine behind the Braillia experience.
  • H2: Turn inaccessible workflows into accessible experiences.
  • H2: Provide accessibility without assembling everything from scratch.
  • H2: Connect organizations to the people they serve.
  • H3: Assisted document intake
  • H3: Mobile understanding
  • H3: Reminders and next steps
  • H3: Assisted delivery workflows
  • H3: No-code accessibility delivery through the Braillia Portal.
  • H3: Centralized control through Company Admin.
  • H3: Enterprise API integration for existing systems.
  • H3: Systems Braillia can connect to
  • H3: Delivery actions Braillia can automate
  • H3: Manage organization account settings
  • H3: Add and manage authorized users
  • H3: Assign admin and user roles
  • H3: Update organization logos and branding
  • H3: Review subscription and billing access
  • H3: Support document publishing workflows
  • H3: Manage mobile delivery access
  • H3: Prepare teams for accessible delivery at scale
  • H2: Built for the moments where accessibility matters most.
  • H3: Secure document delivery
  • H3: Retention and expiration controls
  • H3: Organizational branding
  • H3: Account and role management
  • H3: Document activity visibility
  • H3: Scalable delivery operations
  • H2: Start with a high-impact document pilot.
/accessible-documents-for-blind-users9 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: Clear answers for accessibility teams.
  • H1: A trusted information companion for blind and low-vision users.
  • H2: Built to feel calm, consistent, and guided
  • H2: Get answers when information feels confusing
  • H2: Never lose track of important dates hidden inside documents
  • H2: Read everyday printed information more independently
  • H2: Stay connected to important updates
  • H2: Keep important information organized and accessible
  • H2: Start with a high-impact document pilot.
/compliance-solutions8 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: Wherever information matters, accessibility matters.
  • H2: Common workflows where urgency shows up.
  • H2: Clear answers for accessibility teams.
  • H1: Start where urgency matters most.
  • H2: Utilities
  • H2: Healthcare
  • H2: Public and regulated services
  • H2: Start with a high-impact document pilot.
/mobile-experience45 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: Each area starts simple, then opens into deeper usability context.
  • H1: One accessible place for the information life depends on.
  • H2: Braillia Options
  • H3: Full detail
  • H2: Scan Code
  • H3: Full detail
  • H2: Braillia Documents
  • H3: Full detail
  • H2: Document Reader
  • H3: Full detail
  • H2: Braillia Personal Assistant
  • H3: Full detail
  • H2: Braillia Messages
  • H3: Full detail
  • H2: Organization Requests
  • H3: Full detail
  • H2: Braillia Reminders
  • H3: Full detail
  • H2: Read Printed Text
  • H3: Full detail
  • H2: Low Vision Assist
  • H3: Full detail
  • H2: Product Information Barcode Access
  • H3: Full detail
  • H2: Personal Setup
  • H3: Full detail
  • H2: Braillia Setup
  • H3: Full detail
  • H2: Low Vision Screen Settings
  • H3: Full detail
  • H2: Braillia Suggestions
  • H3: Full detail
  • H2: Help Center
  • H3: Full detail
  • H2: Guided Accessibility
  • H3: Full detail
  • H2: Swipe Navigation
  • H3: Full detail
  • H2: Top Navigation
  • H3: Full detail
  • H2: Secure Organization Delivery
  • H3: Full detail
  • H2: Overall User Benefit
  • H3: Full detail
  • H2: Start with a high-impact document pilot.
/on-demand-accessible-documents6 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H2: Clear answers for accessibility teams.
  • H1: Real-time mobile access from digital inputs.
  • H2: From document delivery to usable access
  • H2: No waiting when information matters
  • H2: Built for BLV workflows
  • H2: Start with a high-impact document pilot.
/privacy-policy9 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H1: Privacy Policy.
  • H2: What this policy covers
  • H2: Information you provide
  • H2: Form processing
  • H2: Local storage and site preferences
  • H2: Analytics and marketing technologies
  • H2: How we use information
  • H2: Your choices
  • H2: Related policy
/cookie-policy8 headings, 5 landmarks

Landmarks

  • banner: 1
  • navigation: 2 (Main navigation, Footer navigation)
  • main: 1
  • contentinfo: 1

Heading outline

  • H1: Cookie Policy.
  • H2: Current tracking status
  • H2: Storage used today
  • H2: Consent categories
  • H3: Strictly necessary
  • H3: Analytics
  • H3: Marketing
  • H2: Changing your choices

Route results

Results by page.

Clear
Accessibility scan summary by page route
RouteStatesAxeBrailliaStatus
/600Clear
/accessibility-scan-report600Clear
/accessibility-compliance600Clear
/accessibility-compliance-vs-usability600Clear
/accessibility-delivery-platform600Clear
/accessible-documents-for-blind-users600Clear
/compliance-solutions600Clear
/mobile-experience600Clear
/on-demand-accessible-documents600Clear
/privacy-policy600Clear
/cookie-policy600Clear

Human verification

Manual Verification Queue.

Automated and AI-assisted testing can collect evidence. Use this queue to verify or certify judgment-based items with a named reviewer, timestamp, notes, and exportable evidence.

Certified

0

Verified

0

AI Suggested

0

Manual Review

7

Needs Revision

0

Not Applicable

0

Hero image alt text quality

/WCAG 1.1.1 Non-text Content
Manual ReviewOpen details
Criteria
WCAG 1.1.1 Non-text Content
Element
Homepage hero image showing mobile QR access to a hospital billing statement
Standards
Section 508 E205.4, EN 301 549 9.1.1.1
Verification prompt
Confirm the alt text explains the purpose of the image, not just its appearance.

Alt text should describe the meaningful action: a blind or low-vision user scanning a Braillia QR code to access a hospital billing statement.

Manual pass requirements

  • Meaningful images have text alternatives that serve the same purpose as the image.
  • Decorative images are hidden from assistive technology or have empty alt text.
  • The hero image alt describes the user action and purpose: QR pickup into accessible hospital billing access.
  • Alt text is concise enough to be usable but specific enough to preserve meaning.

Required evidence

  • Record the final alt text.
  • Record reviewer confirmation that the text alternative serves the same purpose as the image.

Certification test steps

  1. 1Inspect the hero image alt attribute.
  2. 2Review the image in page context and identify what information or action it communicates.
  3. 3Confirm the alt text communicates that same purpose to a non-visual user.
  4. 4Confirm no decorative dots, gradients, or icons add noisy alt text.

Tools: Browser inspector, Screen reader or accessibility tree proxy

Certify records this manual item as reviewed by the named reviewer.

Responsive reading order

All scanned routesWCAG 1.3.2 Meaningful Sequence
Manual ReviewOpen details
Criteria
WCAG 1.3.2 Meaningful Sequence
Element
Page content order at desktop, mobile, and 320 pixel reflow widths
Standards
Section 508 E205.4, EN 301 549 9.1.3.2
Verification prompt
Use keyboard and screen reader navigation to confirm the content sequence remains logical.

Automated scans found no horizontal overflow. Manual review should confirm the reading order still makes sense visually and with assistive technology.

Manual pass requirements

  • Content order preserves meaning when read sequentially.
  • Responsive layouts do not change the reading order in a way that confuses the meaning.
  • Headings, cards, CTAs, and supporting text are encountered in a logical sequence.
  • No important content is skipped, duplicated unexpectedly, or read before required context.

Required evidence

  • List the routes and viewport sizes reviewed.
  • Record whether the sequence remained understandable across each reviewed state.
  • Note any sections where visual order and spoken order need adjustment.

Certification test steps

  1. 1Review the homepage, report page, mobile experience page, and compliance page at desktop width.
  2. 2Repeat at mobile width and 320 pixel reflow.
  3. 3Use Tab and assisted reading order to move through content from top to bottom.
  4. 4Compare the spoken or accessibility-tree order with the visual layout and document outline.

Tools: Keyboard, Browser accessibility tree report, NVDA, VoiceOver, or comparable assistive technology when available

Certify records this manual item as reviewed by the named reviewer.

Link purpose clarity

Global navigation and page CTAsWCAG 2.4.4 Link Purpose
Manual ReviewOpen details
Criteria
WCAG 2.4.4 Link Purpose
Element
Mega menu links, footer links, CTA links, and report links
Standards
Section 508 E205.4, EN 301 549 9.2.4.4
Verification prompt
Check repeated links and CTA labels out of context to confirm users know where they go.

Automated checks confirm links have accessible names. Manual review should confirm each link purpose is understandable in context.

Manual pass requirements

  • The purpose of each link can be determined from link text alone or its programmatically determined context.
  • Repeated links that go to different destinations are distinguishable by text or context.
  • Image/icon links have accessible names that describe the destination or action.
  • Generic labels are acceptable only when nearby programmatic context makes the destination clear.

Required evidence

  • Record any ambiguous link text reviewed and why it is acceptable or revised.
  • Record confirmation that global navigation and page CTAs have clear destinations.

Certification test steps

  1. 1Review header, mega menu, footer, report links, and page CTAs.
  2. 2Check link names out of context where possible.
  3. 3Confirm repeated labels point to the same destination or have enough surrounding context.
  4. 4Activate representative links and confirm they go where the label indicates.

Tools: Keyboard, Browser links list or accessibility tree, Screen reader links list when available

Certify records this manual item as reviewed by the named reviewer.

Web Assist modal flow

Global Web AssistWCAG 2.1.2 No Keyboard Trap
Manual ReviewOpen details
Criteria
WCAG 2.1.2 No Keyboard Trap
Element
Accessibility button, modal controls, standards panel, close behavior, and Begin Page Reading
Standards
WCAG 2.1.1 Keyboard, Section 508 E205.4, EN 301 549 9.2.1.2
Verification prompt
Open Web Assist, Tab through controls, toggle each option, close it, and confirm voice prompts stop.

Automated checks confirm visible controls have names. Manual review should confirm Tab order, Escape behavior, close behavior, and voice prompt accuracy.

Manual pass requirements

  • Keyboard focus can enter the Web Assist panel and move through every control.
  • Focus is not trapped without an available keyboard method to leave or close.
  • Escape and Close Accessibility close the panel and stop voice prompts.
  • Toggle controls announce or expose their current state.
  • Begin Page Reading starts at the top Braillia logo and Tab/Shift+Tab navigation remains predictable.

Required evidence

  • Record browser and assistive technology used.
  • Record that Tab, Shift+Tab, Enter, Escape, and Close Accessibility were tested.
  • Record any prompt wording issues or confirm none were found.

Certification test steps

  1. 1Open Web Assist from the accessibility button.
  2. 2Use Tab and Shift+Tab through every modal control.
  3. 3Toggle Larger Text, Readable Spacing, High Contrast, and Reduce Motion with Enter.
  4. 4Open and close the standards reference panel.
  5. 5Use Begin Page Reading and confirm focus starts at the top Braillia logo.
  6. 6Close Accessibility and confirm voice prompts stop.

Tools: Keyboard, Browser speech output, Screen reader when available

Certify records this manual item as reviewed by the named reviewer.

Mega menu keyboard flow

Site headerWCAG 2.1.1 Keyboard
Manual ReviewOpen details
Criteria
WCAG 2.1.1 Keyboard
Element
Top-level menu buttons and submenu links
Standards
WCAG 2.4.3 Focus Order, Section 508 E205.4, EN 301 549 9.2.1.1
Verification prompt
Confirm keyboard navigation is predictable and the menu closes when focus leaves the menu path.

The intended behavior is Tab through top-level menu options, Arrow Up/Down inside submenus, and Enter to open selected links.

Manual pass requirements

  • Top-level menu buttons are reachable with Tab in logical left-to-right order.
  • Arrow Down and Arrow Up open and move through submenu links.
  • Tab from a submenu closes the submenu and moves to the next top-level menu button.
  • Escape closes the open menu and returns focus to the related top-level button.
  • Enter activates the selected link without unexpected focus jumps.

Required evidence

  • Record which menu groups were tested.
  • Record confirmation that focus order and menu close behavior matched the intended pattern.

Certification test steps

  1. 1Tab from the Braillia logo through Platform, Solutions, Resources, and Company.
  2. 2Open each menu with Arrow Down.
  3. 3Navigate submenu options with Arrow Down and Arrow Up.
  4. 4Use Tab to leave the submenu and confirm it closes.
  5. 5Use Escape on an open submenu and confirm focus returns correctly.
  6. 6Activate representative submenu links with Enter.

Tools: Keyboard, Browser accessibility tree, Screen reader when available

Certify records this manual item as reviewed by the named reviewer.

Contact form labels and instructions

/workflow-reviewWCAG 3.3.2 Labels or Instructions
Manual ReviewOpen details
Criteria
WCAG 3.3.2 Labels or Instructions
Element
Contact form fields, labels, instructions, and submit flow
Standards
Section 508 E205.4, EN 301 549 9.3.3.2
Verification prompt
Confirm required fields, labels, and submission expectations are clear.

Automated checks confirm visible form controls have accessible names. Manual review should confirm the form can be completed without confusion.

Manual pass requirements

  • Each input has a visible label or instruction that tells the user what to enter.
  • Required fields and expected formats are understandable before submission.
  • The submit action is clearly named.
  • The form can be completed with keyboard alone.
  • Status, success, or error messaging is understandable when tested.

Required evidence

  • Record fields reviewed.
  • Record required-field behavior and any submission status message observed.
  • Record whether labels/instructions were sufficient without outside explanation.

Certification test steps

  1. 1Tab through every contact form field.
  2. 2Confirm each field label is visible and understandable.
  3. 3Submit an incomplete form and review any required-field behavior.
  4. 4Submit a representative complete form or test submission path when safe.
  5. 5Confirm the user understands what will happen after submitting.

Tools: Keyboard, Browser inspector, Screen reader or accessibility tree proxy

Certify records this manual item as reviewed by the named reviewer.

Screen reader walkthrough

Core routesAssistive technology usability review
Manual ReviewOpen details
Criteria
Assistive technology usability review
Element
Homepage, report page, mobile experience page, and compliance page
Standards
WCAG supporting evaluation, Section 508 functional performance review, EN 301 549 functional performance review
Verification prompt
Walk the core routes with NVDA, VoiceOver, or comparable assistive technology and record any confusion.

Automated tests cannot fully determine whether the experience feels understandable with a screen reader.

Manual pass requirements

  • Page titles, landmarks, headings, links, and controls are announced clearly.
  • Users can reach main content, navigation, Web Assist, and page CTAs without confusion.
  • The content order supports understanding of the page purpose and available actions.
  • Dynamic Web Assist behavior does not continue speaking after accessibility is closed.
  • Any limitations or assistive technology differences are recorded.

Required evidence

  • Record assistive technology and browser used.
  • Record routes reviewed.
  • Record whether headings, landmarks, menus, modal controls, and CTAs were understandable.
  • Record any issues found or confirm no issues were found.

Certification test steps

  1. 1Review the homepage, accessibility scan report, mobile experience page, and accessibility compliance page.
  2. 2Use heading navigation, landmark navigation, link navigation, and Tab navigation.
  3. 3Open and close Web Assist.
  4. 4Begin page reading and move through the page with Tab and Shift+Tab.
  5. 5Record any confusing labels, repeated phrases, missing context, or unexpected focus movement.

Tools: NVDA, VoiceOver, JAWS, TalkBack, Orca, or browser accessibility tree proxy if full AT is not available

Certify records this manual item as reviewed by the named reviewer.

Detailed findings

Every scanned state.

/ - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/ - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/ - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/ - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/ - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/ - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-scan-report - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-scan-report - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-scan-report - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-scan-report - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-scan-report - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-scan-report - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance-vs-usability - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance-vs-usability - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance-vs-usability - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance-vs-usability - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance-vs-usability - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-compliance-vs-usability - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-delivery-platform - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-delivery-platform - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-delivery-platform - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-delivery-platform - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-delivery-platform - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessibility-delivery-platform - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessible-documents-for-blind-users - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessible-documents-for-blind-users - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessible-documents-for-blind-users - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessible-documents-for-blind-users - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessible-documents-for-blind-users - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/accessible-documents-for-blind-users - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/compliance-solutions - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/compliance-solutions - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/compliance-solutions - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/compliance-solutions - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/compliance-solutions - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/compliance-solutions - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/mobile-experience - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/mobile-experience - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/mobile-experience - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/mobile-experience - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/mobile-experience - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/mobile-experience - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/on-demand-accessible-documents - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/on-demand-accessible-documents - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/on-demand-accessible-documents - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/on-demand-accessible-documents - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/on-demand-accessible-documents - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/on-demand-accessible-documents - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/privacy-policy - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/privacy-policy - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/privacy-policy - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/privacy-policy - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/privacy-policy - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/privacy-policy - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/cookie-policy - light - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/cookie-policy - dark - desktopNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/cookie-policy - light - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/cookie-policy - dark - mobileNo issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/cookie-policy - light - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.

/cookie-policy - dark - reflow-320No issues found

No automated Axe violations or Braillia custom check findings were reported for this page state.