Identity
Operator and scope
Organization, domain, public contact details, address and an optional introduction.
Accessibility Statements
Create a Clearer Statement—and Keep It Easier to Maintain
SimplifyAccess turns statement setup into a guided workflow. Work through the operator, statement structure, context, assessment, barriers, feedback and publication without facing every possible field at once.
Maintain the information in one place, then make the current saved statement available as public HTML, an embedded statement, an on-demand PDF or a PDF download through the SimplifyAccess widget.
Built for ongoing maintenance
A Statement Should Not Become Stale the Day It Is Published
Accessibility statements often begin as a copied template or a PDF assembled for one deadline. That makes later updates easy to miss and creates distance between what the organization maintains and what visitors actually see.
Maintain one source
Keep operator, assessment, barrier, feedback and publication information together.
Generate from current saved data
Public outputs use the maintained statement and enabled widget configuration when requested.
Review the facts as the website changes
Request-time generation does not replace organizational review of manually entered information.
Guided creation
From the First Question to a Publishable Statement, One Step at a Time
The editor uses eight focused steps. What appears next depends on the statement structure, context, assessment status and answers already provided, so specialist fields do not crowd every customer from the start.
Operator
Who is responsible and what website or service does the statement cover?
Statement type
Choose general transparency, public-sector or consumer-service information.
Legal context
Use a supported starting point or enter the exact jurisdiction and basis manually.
Assessment
Record status, benchmark, method, dates and an evaluation report where available.
Content
Describe measures, known barriers, alternatives, exceptions and planned improvements where relevant.
Feedback
Provide the route visitors can use to report a barrier or request help.
Authority or procedure
Add a verified escalation, complaint, enforcement or market-surveillance route where applicable.
Review and share
Check completeness, review the entered information and use the publication options.
Quick Start
Start With What You Know
If the basic context is already clear, Quick Start reduces the first setup to three choices: statement structure, country or jurisdiction, and legal or voluntary context.
SimplifyAccess prepares a neutral baseline, suggests relevant fields and then takes the customer to the first remaining gap. It deliberately leaves conformance as Not assessed instead of creating a confident-looking result from minimal information.
- Useful defaults without locking the statement text.
- Preparation date can be set where appropriate.
- No invented assessment result or automatic legal classification.
What the statement can contain
Explain the Current Situation Without Hiding the Gaps
The finished statement can combine identity, assessment evidence, known barriers, alternatives, feedback and context-specific information in one structured public document.
Evidence
Assessment and status
Status, benchmark, method, assessment date, review date and evaluation report where available.
Transparency
Barriers and alternatives
Known inaccessible content, accessible alternatives, applicable exceptions and planned improvements.
Support
Feedback and escalation
Feedback route, expected response time and a verified complaint, enforcement or other procedure where relevant.
One maintained source
One Maintained Statement, Four Ways to Offer It
The publication options come from the same saved statement. Choose the format that fits the visitor journey instead of maintaining separate copies for each channel.
Maintained in SimplifyAccess
The statement source
Operator details, statement structure, legal context, assessment, barriers, alternatives, feedback and procedures remain in one maintained record.
Saved statement information
Current enabled widget features
Request-time generation timestamp
Generated output reflects the current saved information at request time. Manually entered facts still need regular review.
Public HTML
Link directly to the statement
A semantic, responsive page that can be read directly in the browser and shared through its public URL.
/statements/...
Embedded statement
Place it inside your own page
A style-free vanilla JavaScript embed creates semantic HTML and inherits the customer website's visual design.
<script src="…/accessibility-statement.js">
On-demand PDF
Download or share a portable version
Generate the PDF when needed or copy its direct URL for records, sharing and offline use.
Download PDFCopy PDF URL
Widget access
Make the PDF easy to find in the widget
Visitors can reach the current PDF from a statement download button at the bottom of the SimplifyAccess widget.
Download accessibility statement
Configuration-aware information
The Statement Reflects the Assistance You Actually Provide
When the statement is requested, SimplifyAccess can describe the visitor-facing widget features that are enabled for that website. Hidden, internal or deprecated settings are not presented as visitor assistance.
Less duplicated maintenance
The feature list comes from the website configuration instead of a separate manually maintained marketing list.
Clear about the limits
The statement explains that browser-based assistance supplements accessible design, code, content, documents, testing and remediation.
International and custom contexts
Useful Starting Points. Room for the Exact Context.
Statement structure, jurisdiction and legal context are handled as separate choices. Common contexts can provide editable starting points, while another country, region, law, policy, contract or voluntary basis can be entered manually.
This keeps the workflow useful beyond the built-in preset list and avoids presenting a country selection as an automatic legal decision.
European Union Germany United Kingdom United States Canada Switzerland Australia New Zealand Other / manual context
English German
Transparent by design
Keep the Published Status Tied to the Evidence Behind It
The editor separates what is known from what is still unknown. It can record how and when a website was assessed, describe known barriers and alternatives, and keep an explicit Not assessed state when the evidence is not yet available.
Assessment details stay visible
Standard, method, date and report link can support the declared status where available.
Known barriers can be specific
Partial and non-conformance can require concrete information instead of a generic warning.
Feedback is part of the statement
Visitors can see how to report a problem, request help or use an applicable escalation route.
No automatic conformance claim
A widget, generated document or single automated check is not treated as proof of conformance.
Questions and implementation details
Accessibility Statement FAQ
The main workflow stays product-focused. The details below explain legal-context support, technical delivery and important limitations.
Is SimplifyAccess Statements a legal template or legal advice?
No. SimplifyAccess provides guided statement structures, editable starting points and publication tools. The organization still needs to determine which rules apply, verify the facts it publishes and use appropriate accessibility or legal review where needed.
Does creating a statement make the website conformant?
No. A statement documents accessibility information. It does not make the underlying website accessible, prove conformance or replace remediation and testing with assistive technologies.
What if the website has not yet been assessed?
Use Not assessed. The statement can still publish useful operator, contact, accessibility and visitor-support information without inventing assessment details or a conformance result.
Which statement structures are available?
SimplifyAccess supports general accessibility transparency information, public-sector accessibility statements and consumer-service accessibility information. The statement structure is selected separately from the jurisdiction and legal context.
Which countries and legal contexts have built-in starting points?
Current starting points cover EU public-sector and European Accessibility Act consumer-service contexts; German federal, state/local and BFSG contexts; UK public-sector websites and apps; US federal Section 508 and ADA Title II state/local-government contexts; Canadian federal and Ontario contexts; the Swiss Federal Administration; Australian digital goods and services; and New Zealand government web standards. These are drafting aids, not automatic decisions about legal applicability.
Can I use Statements in another country or for a more specific rule?
Yes. Choose another jurisdiction or name a specific state, province, region or other local scope. You can enter the exact law, regulation, policy, contract or voluntary basis, add scope notes, select or enter the assessment benchmark actually used and provide a custom procedure or authority. Those manual values are included in the public outputs.
Do some contexts add their own fields?
Yes. For example, the US federal context can expose additional accessibility contact, complaint, accommodation, relay-service and policy fields. The Canadian federal context includes a reminder that a website statement does not replace a regulated accessibility plan, feedback-process description or progress report where those are required.
Which languages are currently supported?
The current editor and generated public HTML, embedded statement and PDF output support English and German. Legal-context availability and interface-language availability are separate, so a country preset does not imply support for every local language.
What does Quick Start do?
Quick Start uses the selected statement structure, country or jurisdiction and legal or voluntary context to prepare a neutral starting configuration. It can suggest relevant fields and preparation information, but it keeps conformance as Not assessed and directs the customer to the remaining gaps.
How is statement progress calculated?
Progress is calculated from the fields relevant to the selected statement type, status and context. A partially completed statement can return to the first relevant incomplete step, while a complete saved statement opens at the ready-and-share view. No separate wizard progress record is required.
How can I publish the statement?
The same maintained source can be provided as a public HTML page with its own URL, embedded as semantic HTML inside the customer website, generated as an on-demand PDF with a direct URL, or exposed as a PDF download through the SimplifyAccess widget. The options can be used together.
Does the embedded statement add styles or a framework?
No. The standard embed uses vanilla JavaScript and standard browser APIs to create semantic headings, paragraphs, lists, links, sections and details elements. It injects no CSS, so the host website controls the appearance. The heading level can be configured to fit the surrounding page.
Does the embed work with a restrictive Content Security Policy?
It is designed to work without inline script or inline style. The customer still needs to allow the SimplifyAccess CDN origin in
script-src and the statement API origin in connect-src within the site's existing policy.Is the generated PDF a tagged PDF/UA document?
No. The generated DomPDF file has a clear visual structure but is not automatically a tagged PDF/UA document. Where accessible, machine-readable publication is required, use the public HTML page or semantic embed as the primary version and keep the PDF as an additional portable format.
When is the published statement updated?
Public outputs are generated from the current saved statement when requested. The generation timestamp and enabled SimplifyAccess feature inventory reflect that request. This prevents the publication layer from serving an old stored copy after a saved change, but manually entered facts still need regular organizational review.
Accessibility information that stays manageable
Make the Statement Easier to Create, Maintain and Find
Bring the assessment context, known barriers, visitor support, feedback route and publication options together in one workflow.