Bruce Blaser

It looks like we will need both types of toggles on the Settings page: those that use `button`s and those that use radio button `input`s (as demonstrated in my codepen...

> My argument for the popup. I just like it. > I don't think it would be too difficult to implement. I like it too but I'm going to disagree...

> I think it's OK if it's not totally compliant since this is more of an "extra" feature and not a core feature. I'm not sure I would make that...

If we implement a separate tab in which we can display the terms and definitions then I think we could get away with using the built in browser tooltip functionality...

Technically, I don't think this is a WCAG failure. [Success Criterion 3.2.4](https://www.w3.org/WAI/WCAG21/Understanding/consistent-identification.html) does address consistent identification of functional components. In this scenario, in wide view they are HTML buttons but...

@mmatsumoto1026 Everything is looking good here, nice job. @Sboonny I believe the only way you can "force" the keyboard to stay open is by setting the focus on an element...

@Sboonny I'm not sure I completely understand your idea for keeping the keyboard open when running the tests. Perhaps you should open a new issue for this and explain in...

> Then, height: 100dvh; and height: 100svh; were tested to set for html element's height, but it seems to be invalid in android Chrome now Yep, Chrome on Android does...

When I remove `z-index` from `#years` in the finished product then the content in the table overlaps the years heading (which is using sticky positioning).

Hey, it's me, so you knew I was going to chime in sooner or later. A few accessibility concerns: - The three buttons need to be grouped with an accessible...