Context Navigation

Changes between Initial Version and Version 1 of Ticket #50623, comment 25

initial	v1
1	1	@estelaris thank you for all your really hard work and gentle response to feedback on this. I think we're in a good place to move into development here. As everyone working on this knows, updates is a bit of a path, but this is going to be a great step on that road.
2	2
3		It's important to note that the text treatment should be the same along with placing on both mobile and desktop, so whilst I think one mock looks like it uses bold, let's avoid that in the development. @audrasjb just looping you in here as this is ready to move and I am going to remove the feedback keyword from design for now. Once there is a patch, we can hop back in and give input.
	3	It's important to note that the text treatment should be the same along with placing on both mobile and desktop, so whilst I think one mock looks like it uses bold, let's avoid that in the development along with checkboxes without marks. @audrasjb just looping you in here as this is ready to move and I am going to remove the feedback keyword from design for now. Once there is a patch, we can hop back in and give input.
4	4
5	5	Using a checkbox does bring some cognitive weight with multiples of the same interface, but after a discussion around this the accessibility gains and adaptions we can do in the text we have found a middle ground. That doesn't mean this shouldn't be explored in future versions of auto-updates, but let's get this into the beta!