Accessibility is the subject of this site—and a continuing responsibility.
DOFIW aims to make its tools, articles, and navigation usable by people with diverse abilities, technologies, devices, and preferences. This statement describes the current goal, honest assessment status, measures taken, known limitations, and way to report a barrier.
Published: September 1, 2026A usable website, not only accessibility advice
DOFIW creates resources about web accessibility, but subject matter alone does not make a website accessible. This statement covers the site’s articles, navigation, supporting pages, and the interactive resources listed in the Accessibility Tools directory. The site operator is responsible for examining DOFIW’s own content, controls, generated examples, and publishing workflow.
The aim is to remove barriers when they are identified, communicate limitations openly, and avoid making a conformance claim that has not been supported by an appropriate evaluation.
Target: WCAG 2.2 Level AA
The Web Content Accessibility Guidelines define testable requirements at Levels A, AA, and AAA. DOFIW uses WCAG 2.2 Level AA as its current accessibility target.
“Not assessed” means a sufficiently complete evaluation result is not yet available. It does not mean that every page fails, and it does not mean that the site conforms. Individual design decisions and focused checks are not a substitute for evaluating all applicable success criteria across a representative website scope and complete processes.
After a documented assessment, this section should be updated with the evaluated scope, date, method, result, known exceptions, and supporting evidence.
Accessibility practices built into the resource format
Current design and editorial measures include:
Semantic page organization
Pages use one primary heading, descriptive section headings, native controls, labels, lists, tables, and landmarks where appropriate.
Keyboard-operable controls
Interactive elements are intended to work without a pointer and include visible focus treatment within the custom page content.
Responsive and zoom-aware layouts
Layouts adapt to narrower screens, avoid fixed content widths, and use text that can reflow within the scoped designs.
Reduced-motion consideration
Navigation behavior checks the user’s reduced-motion preference where smooth scrolling is used.
Specific names and explanations
Links and controls aim to describe their destination or action, while tool results include interpretation and limitations.
Focused local processing
Tool inputs are designed to be processed in the browser without requiring an account or external analysis API.
Technologies used by the website
DOFIW relies on web technologies supported by browsers and assistive technologies:
HTML provides content and structure, CSS controls presentation and responsive layout, and JavaScript powers tool calculations and selected interface behavior. WAI-ARIA is used only where native HTML does not provide enough accessible information.
Core article content should remain readable without JavaScript. The calculators, checkers, generators, copy actions, and JavaScript navigation buttons require JavaScript to perform their interactive functions.
Browsers and assistive technologies
DOFIW is intended for current standards-based browsers on desktop and mobile devices, including use with keyboard navigation, browser zoom, and assistive technologies that support modern HTML, CSS, and JavaScript.
A formal compatibility matrix covering named browser, operating-system, screen-reader, voice-control, and magnification versions has not yet been completed. Consequently, DOFIW does not currently guarantee compatibility with a particular combination.
Very old browsers, disabled JavaScript, aggressive content blockers, browser extensions, translated overlays, or modifications introduced by the WordPress theme may affect presentation or tool behavior.
Areas that need continued review
Because the complete site has not been formally assessed, this list should not be interpreted as a complete inventory of barriers.
Interactive tools
Tool behavior varies in complexity, and some state changes, validation messages, color previews, generated results, or clipboard notifications may need further testing across different screen readers and voice-control systems. If a control does not communicate its result, email the input and observed behavior for investigation.
Color-based demonstrations
Some resources intentionally demonstrate passing and failing color combinations. Text explanations and numerical values are provided so the demonstration does not rely only on perceiving the color difference.
Third-party advertising and consent interfaces
When enabled, advertisements and privacy messages are supplied through third-party systems. Their content and behavior may change independently of the page. Report a specific barrier with the page address and, if safe, a screenshot.
WordPress theme and publishing changes
The active theme, WordPress updates, inserted advertising, and later editing can alter headings, focus styles, spacing, contrast, or responsive behavior after custom content has been tested.
External destinations
DOFIW cannot control the accessibility of external websites. When a primary source is inaccessible, contact DOFIW for help identifying the referenced information or another route to it.
Current review and future evidence
Individual resources have undergone development checks focused on their markup, responsive presentation, keyboard-oriented controls, input and output behavior, and topic-specific logic. This work is an internal self-review, not an independent audit and not a complete WCAG conformance evaluation of dofiw.com.
A future complete assessment should include representative pages and states, all applicable WCAG 2.2 Level A and AA success criteria, keyboard testing, zoom and reflow, multiple browsers, relevant assistive technologies, generated results, errors, advertising states, consent interfaces, and complete user processes.
W3C provides guidance for developing accessibility statements and for evaluating web accessibility.
Report an accessibility barrier
Email contact@dofiw.com. A useful report includes:
- the address and title of the affected page;
- the task you were trying to complete;
- what happened and what you expected;
- your browser, device, and assistive technology when relevant;
- a screenshot or short error message when safe and helpful.
Do not include passwords, confidential code, customer data, or unrelated sensitive information. Messages are reviewed as resources allow; a fixed response time is not currently promised.
Keeping this statement useful
This statement should be reviewed after significant theme, navigation, tool, advertising, or consent-interface changes and at least once each year. The publication date and assessment status should be revised when new evidence becomes available.
For general contact information, visit the Contact DOFIW page. Information about visit data and local tool processing is available in the Privacy Policy.
This statement was structured using the types of information recommended by the W3C Web Accessibility Initiative’s Accessibility Statement Generator. DOFIW is independent and is not affiliated with or endorsed by W3C.