Every Friday, this blog takes one chapter of Strategic Web Management and argues its central idea, paired with the podcast episode and worksheet built from it. Last week was Chapter 5 and the question of what a platform costs to leave. This week is Chapter 6, Design, UX, and Accessibility Basics, and its idea can be stated in one line: the phone version of your website is not a version. It is the site.

That sounds like a design opinion, and the chapter is careful to show that it is a traffic fact. Mobile devices carry the majority of visits for most small-organization sites, and for local businesses found through search, the share runs higher still. Once your own number is in front of you, the chapter's larger claim follows: the three disciplines that most intimidate accidental web managers, design, mobile, and accessibility, are systems rather than talents, and systems can be learned in a chapter.

Where the chapter starts

Chapter 6 opens with a project from around 2008, a nonprofit whose own board member could not use the organization's website. His screen reader met a page with no alt text, no logical tab order, and no way to reach the navigation without a mouse. I went back through that site adding descriptions to every image and restructuring the navigation until it worked for the person it had failed. That is where accessibility stopped being a compliance word for me and became a person I had let down without meaning to. Chapters 1 through 5 secure things; Chapter 6 turns around and faces the people walking in.

Brand without a brand team

The first system is a minimum viable brand kit: one folder with the logo in the formats people actually request, and one page with two fonts, four hex codes, a sentence of photo guidance, and a few lines on tone. The chapter's real contribution is enforcement: set the website theme to the kit once, lock Canva templates to its palette, and the consistent path becomes the effortless one. None of it requires taste.

The phone test, and what belongs at the top

Responsive templates guarantee that a site fits a phone, not that it works in a hand. Chapter 6 covers readability, touch targets roughly the size of a physical key, and thumb reach, then makes a point most organizations miss: the first screenful is the most valuable property on the site, and most sites spend it on a welcome banner while the hours and the phone number wait below. The ten-minute walk with your own phone produces the design to-do list without an agency invoice.

Eight fixes and one honest warning

Accessibility in the chapter is a short list rather than a specialty: alt text, contrast, real headings, link text that says where it goes, keyboard operability, visible form labels, captions, and never letting color alone carry meaning. Each is an editing-screen repair. The chapter anchors the work to the Web Content Accessibility Guidelines (WCAG) at Level AA and asks the question a board member would: if one in four of your visitors found the front door locked, how long would you leave it that way?

The warning concerns accessibility overlays, the widgets sold as one-line compliance. They cannot repair the structure assistive technology depends on, and organizations running them still appear in complaints. The chapter calls an overlay a sticker over the lock, and the eight fixes cost less.

Hiring help without getting fleeced

The fourth section is for the day the job outgrows you. Green flags include a designer who asks about goals and budget before showing anything, quotes an itemized proposal, answers the WCAG question without flinching, and puts in writing that every account and file ends up owned by your organization. Red flags are the mirror image. Payments tie to milestones, and the final payment buys the handoff: credentials in the vault, source files in organizational storage, every new account in the inventory.

The mission tie-back

While the chapter is filed under design, none of it is about aesthetics. A website is an organization's most public act of hospitality, offered around the clock to people its staff will never meet. The readable text, the reachable button, the described image, and the caption are each a way of saying that whoever arrives is welcome and expected. Episode 7 of The Web Managers Podcast, walks the same ground.

Get the chapter worksheet. The M6.1 10-Point Accessibility and Mobile Self-Audit, with the brand kit template, is the worksheet for Chapter 6 and Episode 7, free with a Web Managers account at https://webmanagers.com/register. The full chapter, with the eight fixes and the hiring section, is in Strategic Web Management: First Steps for the Accidental Web Manager.

Categories

Fundamentals  

Terms