Skip to content

Conversation

@LauraLangdon
Copy link
Contributor

Will close Issue #198.

@LauraLangdon LauraLangdon added the docs-needed Updates to docs for new or revised features label Dec 13, 2022
@LauraLangdon LauraLangdon self-assigned this Dec 13, 2022
@LauraLangdon LauraLangdon linked an issue Dec 13, 2022 that may be closed by this pull request
@vercel
Copy link

vercel bot commented Dec 13, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 18, 2023 6:24pm
docs-beta ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 18, 2023 6:24pm

@github-actions
Copy link

4 total issues, 0 errors, and 4 warnings found for docs.suborbital.dev

Details

WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48
<div class="navbar__items navbar__items--right"><a href="https://suborbital.dev...</div>

If this element contains a navigation section, it is recommended that it be marked up as a list.



WARNING WCAG2AA.Principle1.Guideline1_4.1_4_10.C32,C31,C33,C38,SCR34,G206
<a class="skipToContent_fXgn" href="#docusaurus_skipToContent_fallback">Skip to main content</a>

This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion.



WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour
<span id="docusaurus-base-url-issue-banner-suggestion-container" style="font-weight: bold; color: green;">/</span>

Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour.



WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour
<span style="font-weight: bold; color: red;">/</span>

Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour.



📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

remove completed TODOs
* Use the production mode for the go client

* Refine passing in the api key to golang init

* Add curl examples and missing go example
* update terms

access key -> API key
editor token -> session token

* update terms

access key -> API key

* remove extra space
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-needed Updates to docs for new or revised features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hosted SE2 docs

4 participants