# EaseWeb

> Accessibility remediation guides: what goes wrong, how to fix it, and how to verify the fix with a keyboard, screen readers, zoom and forced colors. Free to use, including as context for coding agents. The full outline, including topics still in progress, is at https://easeweb.dev/learn.

## Keyboard and focus

- [A button cannot be reached with Tab](https://easeweb.dev/learn/native-buttons.md): Use a native button with a visible name and the correct type. Keep the existing visual design, add a visible focus state, and test the save result. Test with: keyboard, screen reader, zoom, forced colors.
- [Keyboard focus disappears on a branded button](https://easeweb.dev/learn/visible-focus.md): Replace the removed outline with a visible, theme-compatible indicator. Check differing surfaces, clipping, zoom, and forced colors. Keep native focus behavior. Test with: keyboard, screen reader, zoom, forced colors.

## Forms

- [A form error gives no way to recover](https://easeweb.dev/learn/accessible-form-errors.md): Describe the error in words, associate it with the field, and provide a predictable route to the error. Keep entered values where appropriate and validate on the server. Test with: keyboard, screen reader, zoom, forced colors.

## Dialogs and overlays

- [A modal opens while focus stays behind it](https://easeweb.dev/learn/modal-focus-management.md): Prefer a native dialog opened with showModal(), give it an accessible name, choose suitable initial focus, and verify focus restoration. A custom modal needs equivalent behavior. Test with: keyboard, screen reader, zoom, forced colors.

## Tabs, accordions and disclosures

- [An accordion opens without exposing its state](https://easeweb.dev/learn/accordion-controls.md): Use details/summary for a simple disclosure, or a button inside a heading for a custom accordion. Synchronize expanded state and actual panel visibility. Test with: keyboard, screen reader, zoom, forced colors.

## Optional

- [Services](https://easeweb.dev/services): manual testing, remediation and retests by a Section 508 Trusted Tester.
- [Vendor review](https://easeweb.dev/services/vendor-review): manual testing for sites that already pay for an accessibility widget, scanner or AI auto-fix, showing what still stops people.