While the report says to make sure focused elements can be discernable, this is very heavy-handed visually and will impact the experience for all of our users.

As I mentioned in a previous comment, I'm all for letting browser default styling get us most of the way there (with outline's and default :focus) styling. **If we want to go any further with styling specific focused-upon states, I'd very strongly recommend that we style the focused state for specific scenarios that are known to give our assistive tech users trouble**. These scenarios should be tailored to visually accentuating things based on the specific UI elements and their context involved. These may include:

* Main Nav
* Dropdown Menus
* Course Nav
* Courseware Nav
* links within a body of text
* form fields/labels
* buttons/anchors that visually act as buttons

With that said, can we revisit this on a case-by-case basis rather than placing a very drastic border on all anchor elements regardless of their context? While it may help in some cases with disabled users experiences, it most certainly affects **all** of our users' experiences - and in some cases may not be perceived as an improvement. A more planful approach can get us the benefit of helping assistive tech users understand what's focused while not jarring/alienating all of our users.