Specify 7 substantially conforms to WCAG 2.1 Level AA for its supported web interfaces. We employ semantic HTML, ARIA best practices, and ongoing automated and manual testing to preserve accessibility.
Implemented controls:
Perceivable
- 1.3.1 Info and Relationships
- Native HTML inputs and proper semantics in forms and widgets:
- 1.3.5 Identify Input Purpose
- Autocomplete and spellcheck attributes on inputs:
- 1.4.4 Resize Text
- User-configurable font size, family, background, and color theme:
- Language of Page
- Language set on the HTML element:
Operable
- 2.1.1 Keyboard / 2.1.2 No Keyboard Trap
- Reliable focus management in dialogs, forms, and complex widgets:
- Focus is lost when clicking the “Add” button on forms (#983)
- Focus is lost on form dialog “Save” click (#984)
- Test nested dialogs for accessibility compliance (#2619)
- Improve Tree Viewer’s accessibility (#980)
- Improve Query Builder’s accessibility (#981)
- Opening forms should highlight first field for data entry (#1543)
- Reliable focus management in dialogs, forms, and complex widgets:
- 2.4.3 Focus Order
- Initial focus set to the first actionable field:
- 2.4.4 Link Purpose (In Context)
- Links provide accessible names (visible text or appropriate ARIA):
- 2.4.7 Focus Visible
- Disabled/inactive states avoid ambiguous focus:
- 1.4.13 Content on Hover or Focus
- Tooltips for collapsed navigation improve on focus/hover:
Understandable
- 3.3.1 Error Identification / 3.3.2 Labels or Instructions
- Reliance on native validators and label clarity:
- 3.2.3 Consistent Navigation
- Mark current page in the navbar:
- 3.2.4 Consistent Identification
- Use buttons vs. links appropriately:
Robust
- 4.1.2 Name, Role, Value
- Correct roles, accessible names, and state updates:
- Continuous Testing
- Automated and manual auditing:
Scope and methods
- Scope: This statement covers the Specify 7 web UI. Accessibility of customer-authored content (e.g., custom forms or third‑party embeds) depends on configuration and may be outside our control.
- Methods: Automated audits (Accessibility Insights, ARC Toolkit) and targeted manual testing (keyboard-only and screen reader) for dialogs, forms, navigation, tabular data, and composite widgets.
Status
Most identified accessibility issues in core workflows have been resolved; we continuously monitor and improve complex controls to maintain conformance and prevent regressions.
References and tracking
- Issues on GitHub related to WCAG are labeled “4 - Accessibility,” see Search results (sorted by updated desc)
- Representative links (also cited above):