Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.| TetraLogical
Well structured content helps everybody understand and navigate documents. When coded properly in the HTML, headings, lists, and landmarks help people who use screen readers (software that reads what’s on screen) both scan and navigate pages.| TetraLogical
HTML semantics provide accessibility information about page structure and an element's role, name, and state, helping to convey the nature and purpose of content on web pages. In this post we explore what HTML semantics are, and how they're experienced by people using assistive technologies like screen readers and speech recognition software.| TetraLogical
TalkBack only announces role information for a relatively small number of user interface (UI) elements within native apps. When comparing this behaviour against web content, this can often give the (false) impression that these elements must have been coded incorrectly and therefore need to be "fixed". This blog post looks at when it is acceptable for a role not to be announced, the roles that TalkBack **does** announce, and what this means for conformance to the Web Content Accessibility Gui...| TetraLogical
Most websites have common areas of content like a header and footer, a main content area, and one or more navigation blocks. Sighted people can identify these areas based on the way they're styled and the content they contain, but people who are blind cannot do that quite as efficiently. Landmarks, like headings and lists, offer screen reader users a more comparable experience for identifying and navigating between these areas of content.| TetraLogical