update ideas

master
Tait Hoyem 2 years ago
parent 1453c33b5f
commit b892c41f3d

@ -52,6 +52,8 @@
<li><a href="#10-new-business-idea" id="markdown-toc-10-new-business-idea">10. New Business Idea</a> <ul>
<li><a href="#cost-and-copyright" id="markdown-toc-cost-and-copyright">Cost and Copyright</a></li>
<li><a href="#105-tactile-diagram-creation-tool" id="markdown-toc-105-tactile-diagram-creation-tool">10.5 Tactile Diagram Creation Tool</a></li>
<li><a href="#106-a-slideshow-thingy-but-accessible" id="markdown-toc-106-a-slideshow-thingy-but-accessible">10.6 a “slideshow” thingy, but accessible(?)</a></li>
<li><a href="#107-screen-reader-plugin-ideas-related" id="markdown-toc-107-screen-reader-plugin-ideas-related">10.7 Screen reader plugin ideas related</a></li>
</ul>
</li>
</ul>
@ -308,6 +310,68 @@ make a tool which can do the following:</p>
<p>This seems like something that, if it does exist, is probably proprietary and costs the same as my services would as a whole.</p>
<h3 id="106-a-slideshow-thingy-but-accessible">10.6 a “slideshow” thingy, but accessible(?)</h3>
<p>For every diagram I create, add a “presentation” widget which can take any list of diagrams and present them in an accessible sequence. I will explain.</p>
<p>So imagine you have 5 diagrams of a binary tree, each with a specific action being done to the binary tree to show it changing over time.
So you insert some elements, remove some elements.
Attach an <code class="language-plaintext highlighter-rouge">aria-live</code> region to a comment for each diagram and have hotkeys which can load the next and previous diagram.</p>
<p>So for example you could have a binary tree that looks like:</p>
<ul>
<li>root
<ul>
<li>left child</li>
<li>right child</li>
</ul>
</li>
</ul>
<p>With the label “this is a height=2 perfect binary tree”.
Let the user know somewhere that capslock+alt+n will open the next diagram (or have a button).
When the user presses the button, <code class="language-plaintext highlighter-rouge">aria-live</code> will announce “Notice where the new node was inserted.”, and display the following diagram:</p>
<ul>
<li>root
<ul>
<li>left node</li>
<li>right node
<ul>
<li>right node #2</li>
</ul>
</li>
</ul>
</li>
</ul>
<p>Keep the user on the same positioned node across a new diagram (unless it is a different type).
If the user is focused on “right node” on the first slide, make sure they end up on “right node” on the second slide.
Now the user can navigate with context to where they were previously.
In the case where a diagram has a corollary twin or equivalent diagram to show in some other form: keep the users focus on the correct node in the diagram across a move to a new “slide”?</p>
<p>Probably easy to do if I tag every diagram node with <code class="language-plaintext highlighter-rouge">id: "abc123"</code> and do the same on the next diagram.
If there is a matching <code class="language-plaintext highlighter-rouge">node_id</code> attribute on the new diagrams elements, then focus there automatically.</p>
<h3 id="107-screen-reader-plugin-ideas-related">10.7 Screen reader plugin ideas related</h3>
<p>Use an Odilia/NVDA plugin to make some of this content even <em>more</em> accessible!
Who says open-source cant have vertical integration?</p>
<p>Ok so something like <code class="language-plaintext highlighter-rouge">.patch</code> files can be hard to read, even for sighted individuals, but perhaps with more integration on a screen reader level,
you could get earcons for addition, removal and stationary lines of code.</p>
<p>Another example:</p>
<p>Perhaps a screen reader user wants to know what type of syntax is being highlighted, this is pretty easily done, even on a static site, with CSS highlighting and a good syntax highlighter which can parse your text and turn it pretty with <code class="language-plaintext highlighter-rouge">span</code> elements.
Now, what if, through a plugin, you could hit something like <code class="language-plaintext highlighter-rouge">CapsLock+Alt+T</code> to get the type of token you are currently focused on (i.e., “variable”, “function”, “object”, “struct”, “class”, “keyword”, etc.)
Im not sure if this one is useful at all, I just know I like my syntax highlighting lol!</p>
<p>I bet there are a TON of uses for vertical integration through NVDA/Odilia plugins.
I will keep writing them down somewhere here….
It really depends on the target audience as Odilia is targeted to <em>already</em> technical people and NVDA is primary used by Windows users—this is to say that an NVDA users will, on average, be less technical than an Odilia user.</p>
</main>
<hr>

Loading…
Cancel
Save