Accessibility testing

Braillia Website Accessibility Transparency.

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, Braillia Accessibility App controls, and the Read Page start point.

Routes checked
11
Landmarks exposed
55
Headings exposed
305
Accessibility App start
Not available

Proxy report generated: Aug 22, 2026, 8:15 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: See where people are blocked from reading, deciding, and acting.
  • H2: Accessibility is an organizational responsibility.
  • H2: One path from inaccessible information to usable access.
  • H3: INFORMATION ENTERING BRAILLIA
  • H3: USABLE ACCESS PATHS
  • H2: Start with the access barrier your users face today.
  • H2: Give people accessible information in the format and experience that works for them.
  • H2: Enterprise controls that protect the human outcome.
  • H3: Protected information handling
  • H3: Evidence that stays connected
  • H3: Built around existing operations
  • H2: Choose the accessibility outcome your team needs to deliver.
  • H2: Get the answers your team needs to move forward.
  • H2: Find the barrier before it becomes a failed task or complaint.
  • H1: Make critical information accessible, usable, and ready when it matters.
  • H2: Reveal what blocks users
  • H2: Give people usable formats
  • H2: Reach people securely
  • H2: Connect the systems your teams use
  • H3: A task stops at the website.
  • H3: The PDF blocks usable access.
  • H3: The information arrives too late.
  • H3: The system produces inaccessible communication.
  • H3: Identify
  • H3: Remediate
  • H3: Verify
  • H3: Rebuild the information into a usable experience.
  • H3: Accessible files for the technology people already use.
  • H3: Guided mobile support when understanding and action matter.
  • H3: Use Braillia in your organization
  • H3: Bring Braillia into your platform or service
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H3: Assess
  • H3: Transform
  • H3: Deliver
  • H3: Operate
  • H3: Understand accessibility exposure
  • H3: Transform inaccessible documents
  • H3: Add accessibility inside a website
  • H3: Modernize legacy communications
  • H3: Bring Braillia into a platform or service
  • H3: Prepare technical and procurement review
/accessibility-scan-report19 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Accessibility breaks in more places than a single web page.
  • H2: A report that turns findings into action.
  • H2: The report can lead directly into the right Braillia solution.
  • H1: Find the barriers before your users have to fight through them.
  • H3: Website barriers
  • H3: PDF and document barriers
  • H3: Critical communication gaps
  • H3: Real user support path
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: Combine automated findings with the evidence teams need to act.
  • H3: Fix the source
  • H3: Support the live website
  • H3: Deliver usable information
  • H2: Ask Braillia to review one public page, PDF, document, or customer communication path.
  • H3: Important note
/accessibility-compliance39 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Accessibility is the ability to use the information.
  • H2: The rules point from technical requirements to a usable delivery outcome.
  • H2: Connect European accessibility requirements with privacy-aware delivery.
  • H2: Requirements are fulfilled when users can independently use the information.
  • H2: Get the answers your team needs to move forward.
  • H1: Accessibility requirements matter. Braillia turns them into usable access.
  • H3: Perceivable
  • H3: Operable
  • H3: Understandable
  • H3: Robust
  • H3: WCAG principles
  • H3: Section 508 programs
  • H3: ADA Title II web and mobile rules
  • H3: EN 301 549 alignment
  • H3: Document accessibility
  • H3: Assistive technology support
  • H3: Effective communication
  • H3: Standards
  • H3: Secure delivery
  • H3: Document structure
  • H3: Mobile access
  • H3: User questions
  • H3: User action
  • H3: Connected workflows
  • H3: Measured outcomes
  • H2: Compliance explains the requirement. Usability proves the outcome.
  • H2: Review the standards behind Braillia's accessibility approach.
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: Braillia turns accessibility requirements into a usable access path.
  • H2: Document accessibility depends on structure users can actually move through.
  • H2: Prove the access path with one critical workflow.
  • H3: Structure the information
  • H3: Deliver access in real time
  • H3: Support understanding
  • H3: Preserve operational control
/accessibility-compliance-vs-usability48 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Technical accessibility establishes the foundation. The user's outcome completes the work.
  • H2: Remediation matters. It has to be connected to the access path.
  • H2: Years of accessibility work have built important foundations. User barriers remain.
  • H2: Information exists. The access path must carry it through action.
  • H2: Connect repaired information to the moment a person understands and acts.
  • H2: Complete the work by connecting document repair to timely, usable delivery.
  • H2: Carry accessible information through every step until the person can receive, understand, and act on it.
  • H2: Get the answers your team needs to move forward.
  • H1: Compliance and remediation create the foundation. Usable access completes it.
  • H3: Accessibility requirements
  • H3: Document remediation
  • H3: Tags and reading order
  • H3: Headings and structure
  • H3: Alt text and link purpose
  • H3: Validation and audit workflows
  • H3: Document accessibility plus delivery
  • H3: A complete access path
  • H3: Voice-guided mobile use
  • H3: Braillia AI Personal Assistant
  • H3: Action support
  • H3: Delivery evidence
  • H3: Web accessibility remains fragile at scale.
  • H3: User experience progress remains too slow.
  • H3: Quick-fix overlays can miss real usability.
  • H3: PDF accessibility remains structurally difficult.
  • H3: Policies need operational follow-through.
  • H3: Compliance asks: What does accessibility require?
  • H3: Remediation asks: Is the content prepared for access?
  • H3: Braillia asks: Did the person get usable access when it mattered?
  • H3: Remediate
  • H3: Deliver
  • H3: Understand
  • H3: Act
  • H2: See how accessibility requirements connect to a usable delivery path.
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: A compliant document inside a broken access path is still a broken experience.
  • H2: Real access is more than a fixed PDF.
  • H3: When that happens, the user pays for the gap with dependence. The organization pays for the gap with cost, risk, complaints, delays, and preventable service failures.
  • H2: Prove the access path with one critical workflow.
  • H3: Call centers
  • H3: Care teams
  • H3: Branch staff
  • H3: Accessibility teams
  • H3: Escalation paths
/accessibility-delivery-platform27 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Connect every step from assessment to independent use.
  • H2: Solve the barrier in front of the user, then connect the full access path.
  • H2: Bring accessible information into the systems and workflows your teams already use.
  • H2: Accessibility breaks when the next step is blocked.
  • H2: Built for sensitive communication with clear operational controls.
  • H2: Get the answers your team needs to move forward.
  • H1: Turn inaccessible information into access people can use.
  • H3: Find the barriers blocking access.
  • H3: Reconstruct information for accessible use.
  • H3: Preserve evidence of what changed.
  • H3: Use the output where people need it.
  • H3: Scale accessibility through existing operations.
  • H3: Document Center and Portal
  • H3: API and legacy integration
  • H3: Approved website deployment
  • H3: Organization administration
  • H3: Secure delivery paths
  • H3: Role-based organization access
  • H3: Retention-aware workflows
  • H3: Operational visibility
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: Start with the access workflow carrying the greatest consequence.
  • H2: Move from the first barrier to a complete access path.
/accessible-documents-for-blind-users14 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Get the answers your team needs to move forward.
  • H1: One guided mobile place forprepared information users can act on.
  • H2: A calmer starting point for delivered information
  • H2: Voice guidance across the experience
  • H2: Braillia AI when details feel confusing
  • H2: Dates, reminders, and next steps
  • H2: Scanning that becomes understanding
  • H2: Organized access users can return to
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: Prove the access path with one critical workflow.
/compliance-solutions25 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Prioritize the communications where delayed access creates the greatest harm.
  • H2: Get the answers your team needs to move forward.
  • H1: Make critical information usable while people still have time to act.
  • H3: Customer communications
  • H3: Billing and statements
  • H3: Benefits and eligibility
  • H3: Member services
  • H3: Patient communications
  • H3: Public notices
  • H3: Forms and packets
  • H3: Policy and claims
  • H3: Account notices
  • H3: Enrollment materials
  • H3: Service alerts
  • H3: Appointment preparation
  • H3: Product and label information
  • H3: Document delivery workflows
  • H3: Accessibility operations
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: Make bills, notices, healthcare instructions, and deadlines usable when people need them.
  • H2: Prove the access path with one critical workflow.
/mobile-experience40 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: AI-Guided Navigation
  • H1: Give blind and low-vision users one guided place to receive, understand, and act on critical information.
  • H2: One voice-guided place for delivered access, urgent access, and next-step action.
  • H2: Braillia Options
  • H2: Braillia Scan
  • H2: Braillia Documents
  • H2: Document Reader
  • H2: Braillia Personal Assistant
  • H2: Braillia Messages
  • H2: Organization Requests
  • H2: Braillia Reminders
  • H2: Read Printed Text
  • H2: Low Vision Assist
  • H2: BLE Braillia Guide
  • H2: Product Information Barcode Access
  • H2: Personal Setup
  • H2: Braillia Setup
  • H2: Low Vision Screen Settings
  • H2: Braillia Suggestions
  • H2: Help Center
  • H2: Guided Accessibility
  • H2: Swipe Navigation
  • H2: Top Navigation
  • H2: Secure Organization Delivery
  • H2: Overall User Benefit
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H3: Documents
  • H3: Messages
  • H3: Reminders
  • H3: Braillia Scan
  • H3: Braillia AI
  • H3: Low Vision Assist
  • H3: Braillia Pay
  • H3: BLE Guide
  • H2: Show us the mobile access moment that needs immediate attention.
  • H2: Turn prepared information into confident, independent action.
/on-demand-accessible-documents18 headings, 5 landmarks

Landmarks

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

Heading outline

  • H2: Prepared content reaches users directly or through QR setup.
  • H2: Delivery opens the door. Braillia helps users understand what matters.
  • H2: Braillia gives teams direct delivery and QR onboarding.
  • H2: Get the answers your team needs to move forward.
  • H1: Deliver critical information while peoplestill have time to act.
  • H3: Prepare delivery-ready content
  • H3: Send directly when connected
  • H3: Use QR setup for new users
  • H3: Read, ask, save, and act
  • H3: Voice-guided opening
  • H3: Braillia AI document assistance
  • H3: Saved access
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
  • H2: Make the next critical document available when it matters.
/privacy-policy16 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: Workflow review and sample documents
  • H2: Form processing
  • H2: Cookies, local storage, and site preferences
  • H2: Analytics and marketing technologies
  • H2: How we use information
  • H2: Security and retention
  • H2: Your choices
  • H2: Related policy
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY
/cookie-policy13 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
  • H2: PLATFORM
  • H2: SOLUTIONS
  • H2: INDUSTRIES
  • H2: RESOURCES
  • H2: COMPANY

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 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 receiving or scanning 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: direct delivery or QR setup 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.

Braillia Accessibility App flow

Global Braillia Accessibility AppWCAG 2.1.2 No Keyboard Trap
Manual ReviewOpen details
Criteria
WCAG 2.1.2 No Keyboard Trap
Element
Braillia Accessibility button, app controls, app information panel, Ask Braillia, close behavior, and Read Page
Standards
WCAG 2.1.1 Keyboard, Section 508 E205.4, EN 301 549 9.2.1.2
Verification prompt
Open Braillia Accessibility App, 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 Braillia Accessibility App 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.
  • Read Page starts at the top Braillia logo, desktop Tab/Shift+Tab navigation remains predictable, and mobile Previous/Next reading controls work.

Required evidence

  • Record browser and assistive technology used.
  • Record that desktop Tab, Shift+Tab, Enter, Escape, Close Accessibility, and mobile/touch Previous and Next reading controls were tested.
  • Record any prompt wording issues or confirm none were found.

Certification test steps

  1. 1Open Braillia Accessibility App from the accessibility button.
  2. 2Use Tab and Shift+Tab through every modal control on desktop.
  3. 3Toggle Larger Text, Readable Spacing, High Contrast, and Reduce Motion with Enter.
  4. 4Open and close the standards reference panel.
  5. 5Use Read Page 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, Braillia Accessibility App, and page CTAs without confusion.
  • The content order supports understanding of the page purpose and available actions.
  • Dynamic Braillia Accessibility App 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, website accessibility transparency report, mobile experience page, and accessibility compliance page.
  2. 2Use heading navigation, landmark navigation, link navigation, and Tab navigation.
  3. 3Open and close Braillia Accessibility App.
  4. 4Begin page reading and move through the page with desktop Tab/Shift+Tab and mobile/touch Previous and Next reading controls.
  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.