new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

GitHub Primer · all subjects

truncate/accessibility

4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Truncate keyboard accessibility limitation

The component is not accessible to keyboard users because there is no browser-native mechanism to show title tooltips when navigating with a keyboard.

Truncate screen reader accessibility

Screen reader users will be able to read the entire content of the component because the truncation is done purely via CSS.

Truncate alternative implementation patterns

To address truncation shortcomings, consider alternative approaches: use a truncated version of content in your markup rather than relying on CSS truncation, then provide the full content in a subsequent details view or dialog. Alternatively, provide a toggle or user setting that allows users to switch all instances of truncated content to the full, non-truncated version.

Truncate accessibility testing requirement

Whenever truncated content is presented to the user, there must be a way for users to see the content in full that works for all users, including keyboard users.

Give your agent this brain