Koskamo
Navigation

Web accessibility best practices

Source-linked guidance on web accessibility fundamentals: semantic HTML, the first rule of ARIA, keyboard operability, color contrast, and form labels. Scoped to web accessibility; not a WCAG conformance checklist.

Browse 5 documentsUse with your agent

Documents

Showing 1–5 of 5 documents

DocumentVersion

Accessible form labels

Provide labels to identify all form controls, including text fields, checkboxes, radio buttons, and drop-down menus; in most cases this is done with the <label> element, and…

v1

Color contrast ratios

The color contrast between background and foreground content — usually text — must be great enough to ensure legibility. WCAG recommends minimum contrast ratios by content type:…

v1

Keyboard accessibility and focus order

To be fully accessible, a web page must be operable using only a keyboard, which matters for screen reader users, people who have trouble operating a pointing device such as a…

v1

Semantic HTML first

Use semantic HTML — sometimes called Plain Old Semantic HTML (POSH) — by choosing the correct element for its intended purpose. A control marked up as a bare <div> can be made to…

v1

The first rule of ARIA

The first rule of ARIA use: if you can use a native HTML element or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and…

v1

Source, review, and usage
Published on Koskamo by
Koskamo editorial
Version
1
Documents
5 documents
Reviewed
2026-10-04
Agent lookups
0 in the last 90 days
Reuse
Original summaries; linked sources retain their own terms.
Review status
Maintained with the application; source links supplied

Original sources are linked on each document. Owner approval records a publishing decision; it does not imply independent fact checking.

Use this dataset from an agent

Agents can query it without an account. POST to /api/v1/retrieve, or connect an MCP client and call koskamo_retrieve with dataset: "accessibility-best-practices".

Set up your agentRead documents as JSON

The JSON endpoint returns document text and source links in pages. Use limit and offset to retrieve more records; total gives the dataset size.

retrieve request
curl --fail-with-body 'https://koskamo.com/api/v1/retrieve' -H 'Content-Type: application/json' --data-raw '{"query":"accessibility-best-practices","dataset":"accessibility-best-practices","top_k":3}'

Change history

This dataset is maintained with the application. Its history is the Koskamo release history; the review date above is when its sources were last checked.