The rain outside didn’t just fall; it “carried on like a pork chop,” hammering against the corrugated iron roof of the studio. Inside, the air smelled of burnt espresso and ozone. Liam, Dax, and Dev—the Three Best Friends—were locked in a battle against a deadline that felt like hard yakka on a Saturday arvo.
The Philosophy of the Studio
The trio didn’t just build websites; they built gateways. Their manifesto was simple: Writing for Web Accessibility wasn’t an afterthought—it was the foundation.
- Liam (The Content King): He believed that for each web page, one must provide a short title that describes the page content and distinguishes it from other pages. He was currently obsessing over the “Space Teddy Inc.” homepage, ensuring the page name came before the organization name.
- Dax (The Visual Architect): His monitors were filled with color wheels and luminance grids. He knew that foreground text needs to have sufficient contrast with background colors, a rule that applied to buttons and background gradients alike.
- Dev (The Logic Master): Dev lived in the “code order.” He was currently ensuring that the order of elements in the code matched the logical order of the information presented. He often checked this by removing CSS styling to see if the content still made sense.
“If we don’t get this right,” Dev muttered, “we’re just pulling a swifty on every user who relies on a screen reader”.
The Arrival of Elias
When the thud came at the door, it wasn’t the sound of a visitor; it was the sound of a warning. Elias, a retiree known to the boys as a frequent tester of their designs, stood in the doorway. He was a man who lived with low vision, hand tremors, and mild short-term memory loss.
“I couldn’t get through the ‘Space Teddy’ checkout,” Elias panted, his voice shaking. “It was the Shadow of the Raven’s Wing. It’s back.”
Dax went pale. “The Shadow? That’s just a myth developers tell to scare juniors.”
“It’s no myth,” Elias said, leaning on a desk. “It’s a deliberate design to exclude. It’s when a site uses color alone to convey information, like marking required fields in red without an asterisk”. “But this was worse. It was a shroud.”
The Mystery of the Raven’s Wing
The Three Best Friends gathered around Liam’s main terminal. Elias pointed a weathered finger at a specific block of text that seemed to shimmer and fade.
The Raven’s Wing (Definition): A technique used by rogue developers to create “unnecessarily complex” content that bypasses the need for clear and concise sentences. It creates a “lack of headings,” making the document nearly impossible to edit or navigate for assistive technology.
“Look at the code,” Dev whispered. His fingers flew across the mechanical keyboard. “They haven’t just ignored the WCAG requirements. They’ve weaponized them. They’re using ambiguous link text like ‘click here’ to lead users into a loop”.
“And the images,” Dax added, his eyes narrowing. “There’s no meaningful text alternatives. For these informational images, they’ve used empty alt-text as if they were purely decorative”.
The First Clue: The “Superbear” Anomaly
As they dug deeper into the “Raven’s” source code, a name popped up that Liam recognized from a recent news article: Superbear.
“Wait,” Liam said, pulling up a local news site. “I just wrote about this. ‘Superbear saves the day… rescuing a young cat from a tree’”. He looked at the code Dev had unearthed. “The Raven is using the Superbear story as a mask. But look at how they’ve marked it up.”
Dev pointed to the screen:
- They used a
<h2>for the title “Superbear saves the day”. - They included a
<time>tag for “7 Aug 2015”. - But hidden inside an
<aside>was a list of “Related Articles” that didn’t exist in the real world.
“Fair dinkum,” Liam breathed. “These links… ‘Superbear stands for mayor’. That never happened. They’re using WAI-ARIA roles like role="search" to hide a data-mining script”.
The Friends’ Vow
The “Shadow of the Raven’s Wing” wasn’t just a technical glitch; it was a digital wall built to stop people like Lakshmi, the blind accountant, and Ian, the clerk with autism, from accessing the truth.
“We need to audit this entire city’s infrastructure,” Dax declared. “Starting with the contrast ratios of every government portal”.
“And I’ll start rewriting the instructions,” Liam said. “No more unnecessarily technical language. We need to describe input requirements, like date formats, so even someone as stressed as Elias can navigate ‘no worries’”.
“I’ll handle the keyboard accessibility,” Dev added. “I’ll ensure every custom widget, from accordions to buttons, uses tabindex="0" to stay in the navigation order”.
They looked at each other. The task was heaps big, but they were the best in the business.
The Audit Checklist
Before they could head out into the “arvo” to confront the Raven, they had to prep their toolkit.
| Tool | Purpose |
| Contrast Checker | To identify “insufficient” contrast that hides text. |
| Screen Reader | To hear the “info and relationships” hidden in the markup. |
| Responsive Debugger | To see how the “Raven’s” site adapts to a “narrow mobile phone”. |
| Aussie Grit | To ensure they don’t “pull a swifty” on their mission. |
“She’ll be right,” Elias whispered, watching the Three Best Friends work. “As long as you keep the content clear and concise, the shadow can’t win”.
SummerSimo Travel Troubles Notes and The Purring Page 
Leave a comment