About this report
- Name of product
- Specset web application (app.specset.com)
- Product version
- Continuously delivered; this report describes the product as deployed on the report date.
- Report date
- September 1, 2026
- Report version
- 1.0
- Product description
- Specset is an AI-native construction document platform. Teams manage project specifications, drawings, submittals, RFIs, and closeout records; run AI-assisted document review; and search across all project documents from a single web application.
- Contact information
- support@specset.com
- Evaluation methods used
- Source-code audit of the application and its shared component library (August–September 2026); automated static analysis with WCAG-oriented lint rules enforced in continuous integration; manual keyboard-only testing and browser accessibility-tree inspection in Chromium; automated unit tests over accessibility behavior; screen-reader testing with VoiceOver (macOS) in Chrome across key workflows, including navigation, data grids, flyout panels, and the embedded PDF viewer (September 2026).
- Notes
- This report covers the Specset web application. Viewing and annotation of customer-uploaded PDF documents uses a third-party viewer component (Apryse WebViewer); its limitations are noted in the relevant criteria. Specset operates an active accessibility remediation program; items marked “remediation planned” are scheduled for upcoming releases, and this report will be reissued as they land.
Applicable standards and guidelines
This report covers the degree of conformance for the following accessibility standards and guidelines:
- Web Content Accessibility Guidelines 2.0
- Level A: Yes · Level AA: Yes · Level AAA: No
- Revised Section 508 standards
- Yes. The U.S. Federal accessibility standard, published January 18, 2017 and corrected January 22, 2018.
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports
- The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports
- Some functionality of the product does not meet the criterion.
- Does Not Support
- The majority of product functionality does not meet the criterion.
- Not Applicable
- The criterion is not relevant to the product.
- Not Evaluated
- The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.0 success criteria, Level A
The WCAG 2.0 tables also document conformance with the Revised Section 508 standards’ Chapter 5 (503.4 is not applicable to this product) and Chapter 6 as they apply to web content, per E205 and the WCAG2ICT approach.
| Criteria | Conformance | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text ContentLevel A | Partially Supports | Interface images, icons, and icon buttons have text alternatives, and required alternatives are enforced by automated checks in the build pipeline. Customer-uploaded PDF drawings and specifications render in the document viewer as graphical content whose text alternatives depend on the source document; Specset additionally extracts document text, which is available through search and the record views. |
| 1.2.1 Audio-only and Video-only (Prerecorded)Level A | Not Applicable | The product contains no prerecorded audio-only or video-only media. |
| 1.2.2 Captions (Prerecorded)Level A | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded)Level A | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.3.1 Info and RelationshipsLevel A | Supports | Form controls are programmatically labeled with error messages associated to their fields; data tables expose grid semantics; pages are structured with landmarks and headings; composite widgets (tabs, comboboxes, trees, switches) expose their roles, states, and relationships. |
| 1.3.2 Meaningful SequenceLevel A | Supports | Reading and focus order follow the visual order of the page. |
| 1.3.3 Sensory CharacteristicsLevel A | Supports | Instructions do not rely solely on shape, size, location, or sound. |
| 1.4.1 Use of ColorLevel A | Supports | Status and state information is conveyed with text labels and icons alongside color. |
| 1.4.2 Audio ControlLevel A | Not Applicable | The product plays no audio. |
| 2.1.1 KeyboardLevel A | Partially Supports | Core workflows are keyboard operable: navigation, global search, forms, list and record views, dialogs, comboboxes, and review workflows. Exceptions: in-cell editing in the spreadsheet-style estimate and measurement editors currently requires a pointer (the underlying data remains readable and exportable), and drawing-annotation tools in the document viewer are pointer-driven. Remediation planned. |
| 2.1.2 No Keyboard TrapLevel A | Supports | Focus can always be moved away from any component using standard keys; dialogs and panels close with Escape and return focus. |
| 2.2.1 Timing AdjustableLevel A | Supports | The product imposes no time limits on user tasks. |
| 2.2.2 Pause, Stop, HideLevel A | Supports | The product has no auto-playing or auto-scrolling content; progress indicators are exempt, and streaming AI responses appear only in response to a user request and can be stopped. |
| 2.3.1 Three Flashes or Below ThresholdLevel A | Supports | No content flashes. |
| 2.4.1 Bypass BlocksLevel A | Supports | A “Skip to main content” link is the first focusable element, and pages are structured with navigation and main landmarks. |
| 2.4.2 Page TitledLevel A | Supports | Pages have descriptive titles; in-application navigation updates the document title and announces the new page to assistive technology. |
| 2.4.3 Focus OrderLevel A | Supports | Focus order preserves meaning and operability; opening a panel moves focus into it and closing restores focus. |
| 2.4.4 Link Purpose (In Context)Level A | Supports | Link and button purposes are clear from their accessible names in context. |
| 3.1.1 Language of PageLevel A | Supports | The page language is programmatically identified. |
| 3.2.1 On FocusLevel A | Supports | Receiving focus does not initiate a change of context. |
| 3.2.2 On InputLevel A | Supports | Changing a setting does not automatically change context without warning. |
| 3.3.1 Error IdentificationLevel A | Supports | Input errors are identified in text, associated with the field programmatically, and announced to assistive technology. |
| 3.3.2 Labels or InstructionsLevel A | Supports | Inputs have visible labels; required fields and formats are indicated. |
| 4.1.1 ParsingLevel A | Supports | Markup is generated by a component framework producing well-formed documents with unique IDs. |
| 4.1.2 Name, Role, ValueLevel A | Partially Supports | Interface controls expose accessible names, roles, states, and values, including custom comboboxes, switches, tabs, tree and table views, and icon buttons. Exceptions: internal widgets of the third-party PDF viewer and the in-cell editors of the spreadsheet-style grids. Remediation planned for the grid editors; the viewer limitation is tracked with the component vendor. |
WCAG 2.0 success criteria, Level AA
| Criteria | Conformance | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live)Level AA | Not Applicable | The product contains no live synchronized media. |
| 1.2.5 Audio Description (Prerecorded)Level AA | Not Applicable | The product contains no prerecorded synchronized media. |
| 1.4.3 Contrast (Minimum)Level AA | Partially Supports | Text, including secondary text, meets the 4.5:1 contrast ratio. Exception: placeholder text inside empty inputs is currently below 4.5:1; the associated visible labels meet the requirement. Disabled controls are exempt per the criterion. Remediation planned. |
| 1.4.4 Resize TextLevel AA | Supports | Text can be resized to 200% via browser zoom without loss of content or functionality; the layout is responsive. |
| 1.4.5 Images of TextLevel AA | Supports | The interface does not use images of text. Customer-uploaded drawings and documents are content for which the particular presentation is essential. |
| 2.4.5 Multiple WaysLevel AA | Supports | Content is reachable through the navigation menu, breadcrumbs, and a global search available on every page. |
| 2.4.6 Headings and LabelsLevel AA | Supports | Headings and labels describe topic or purpose. |
| 2.4.7 Focus VisibleLevel AA | Supports | All interactive elements show a visible focus indicator during keyboard operation. |
| 3.1.2 Language of PartsLevel AA | Supports | The interface is presented in a single language identified at the page level. |
| 3.2.3 Consistent NavigationLevel AA | Supports | Navigation is consistent across the application. |
| 3.2.4 Consistent IdentificationLevel AA | Supports | Components with the same function are identified consistently, using a shared component library. |
| 3.3.3 Error SuggestionLevel AA | Supports | Validation messages describe how to correct the input where a correction is known. |
| 3.3.4 Error Prevention (Legal, Financial, Data)Level AA | Supports | Destructive and irreversible actions require explicit confirmation; submissions are reviewable and editable before and after saving. |
Chapter 3: Functional Performance Criteria
| Criteria | Conformance | Remarks and explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Core record and workflow functionality is operable non-visually via keyboard and assistive technology. Graphical content of customer-uploaded drawings depends on the source documents; extracted document text is available through search and record views. See 1.1.1 and 4.1.2. |
| 302.2 With Limited Vision | Supports | The application supports 200% browser zoom, meets Level AA text contrast (see the 1.4.3 exception for placeholder text), and offers light and dark themes. |
| 302.3 Without Perception of Color | Supports | Color is never the only means of conveying information. |
| 302.4 Without Hearing | Supports | No hearing is required; the product produces no audio. |
| 302.5 With Limited Hearing | Supports | No hearing is required; the product produces no audio. |
| 302.6 Without Speech | Supports | No speech input is required. |
| 302.7 With Limited Manipulation | Partially Supports | The product is operable through keyboard alone without timed or simultaneous actions, with the exceptions noted under 2.1.1 (spreadsheet-style cell editing and drawing-annotation tools). Remediation planned. |
| 302.8 With Limited Reach and Strength | Supports | Operation requires only standard pointing-device or keyboard input with no strength or reach demands. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Navigation and component behavior are consistent; labels use plain language; destructive actions require confirmation; errors are identified with guidance for correction. |
Chapters 4 and 5
- Chapter 4: Hardware
- Not Applicable. Specset is a software-as-a-service web application and includes no hardware.
- Chapter 5: Software
- Not Applicable. Specset is web content delivered in the user’s browser and is evaluated against WCAG 2.0 in the tables above, per E205. It is not platform software, does not restrict access to platform accessibility services, and respects platform settings such as reduced motion and color-scheme preferences.
Chapter 6: Support documentation and services
| Criteria | Conformance | Remarks and explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Partially Supports | Product documentation covers features and workflows; documentation of keyboard operation and accessibility features is being added. |
| 602.3 Electronic Support Documentation | Partially Supports | Documentation is published as standard HTML at docs.specset.com and is built from the same accessible component standards; a dedicated audit of the documentation site has not yet been completed. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All support documentation is electronic. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Support staff provide information on accessibility and compatibility features on request via the contact address above. |
| 603.3 Accommodation of Communication Needs | Supports | Support is provided through text-based channels (email and in-application messaging), accommodating users’ communication needs. |
Legal information
“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).
This document is provided for information purposes only, and the contents hereof are subject to change without notice. Specset does not warrant that this document is error-free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law. This document does not modify any agreement between Specset and its customers.
© 2026 Specset. Report version 1.0, September 1, 2026. For the current version of this report, visit this page or contact support@specset.com.