IIAAP Audit2d ago · 3 min readRTA Accessibility Audit: A Technical ChecklistA page inventory is a useful starting point for a Registrar to an Issue and Share Transfer Agent (RTA). It is not a sufficient description of the application. The same URL can show an empty form, a vaiaapaudit.hashnode.dev
IIAAP Audit4d ago · 3 min readSEBI Accessibility Audit for IAs and RAsIf you maintain an investment-advice or research service, you may have several frontends but only one client journey. The user moves from a public page to authentication, forms, payment, and a documeniaapaudit.hashnode.dev
IIAAP Audit5d ago · 3 min readChoose an Accessibility Audit PartnerSuppose a screen-reader user can browse a mutual fund's scheme page but cannot tell whether an investment form has accepted an amount. The problem is not captured by a homepage score. It appears only iaapaudit.hashnode.dev
IIAAP AuditOct 19 · 2 min readAccessible Video: Captions and TranscriptsYour video component can render a valid track element and still fail users if the file is out of sync, the player hides its caption control, or a deployment points to an old track. Accessible media neiaapaudit.hashnode.dev
IIAAP AuditOct 16 · 3 min readARIA Mistakes to Catch in Web ComponentsAdding role="button" to a div can change its announced role. It does not provide the browser behavior of a native button. The component still needs keyboard activation, focus handling, and a meaningfuiaapaudit.hashnode.dev
IIAAP AuditOct 15 · 3 min readHow to Write Alt Text for Web ComponentsReusable image components are convenient until every call site gets the same generic alt value. A component cannot know whether the asset is the only label on a button, repeats nearby text, or carriesiaapaudit.hashnode.dev
IIAAP AuditOct 9 · 3 min readAudit Headings and Landmarks in Web AppsA component can look correct in isolation and create a confusing page when assembled with other components. A card may hard-code an h4, a layout may insert another main element, and a mobile header maiaapaudit.hashnode.dev
IIAAP AuditSep 30 · 1 min readEN 301 549 vs WCAGWCAG and EN 301 549 are related standards, but they do different jobs. WCAG defines accessibility criteria for web content. EN 301 549 covers accessibility requirements for ICT products and services. iaapaudit.hashnode.dev
IIAAP AuditSep 29 · 1 min readSection 508 vs WCAGSection 508 and WCAG are often mentioned together in ICT procurement. They are related, but they play different roles. The short version Section 508 is the legal and procurement requirement for U.S. fiaapaudit.hashnode.dev
IIAAP AuditSep 28 · 1 min readGIGW 3.0 AccessibilityGIGW 3.0 sets expectations for Indian government websites and apps. From an implementation perspective, its accessibility focus is closely tied to WCAG 2.1 Level AA. What teams should test A useful re1Iiaapaudit.hashnode.dev
