Access
Accessibility Still Comes First
A model does not get a pass on keyboard access, contrast, or understandable errors.
AI is not an accessibility overlay
We do not add a third-party accessibility widget and call the site compliant. We also do not add a chat panel and call that an accessible alternative to good HTML.
Semantic structure, labels, focus, and contrast are still the work.
Model UI has states
If a feature calls GPT, Gemini, Grok, or Claude, the waiting, success, and error states must be announced and usable without a mouse.
A streaming answer that cannot be paused, copied, or reached by keyboard is a failed feature.
Plain language beats generated density
Models tend to add clauses. Accessibility often means cutting them. We edit for reading level and for people who are skimming on a phone in bad light.
The future site is the one a person can finish, not the one with the longest generated explanation.
Continue
Performance When AI Features Are Added
How to add GPT, Gemini, Grok, or Claude features without wrecking Core Web Vitals or shipping a chat SDK on every page.
Read →Ownership of Prompts, Content, and Outputs
Who owns prompts, drafts, and published pages when GPT, Gemini, Grok, or Claude is part of the website project.
Read →What Building Sites for the Future Means
A concrete definition of a future-ready Alaska website: static delivery, owned source, and optional use of GPT, Gemini, Grok, and Claude.
Read →