I don't think having links disguised as buttons is a bad thing - just as long as they genuinely link to another page. From the accessibility guidelines as quoted above (paraphrased): "Use a link if you're navigating to a predefined page or section; use a button if you're changing information or state"
For example, the "New collection" button creates a new collection *by taking you to the 'Edit collection' page* - I think for a screen reader (for example) styling it as a link makes sense.
I don't think having links disguised as buttons is a bad thing - just as long as they genuinely link to another page. From the accessibility guidelines as quoted above (paraphrased): "Use a link if you're navigating to a predefined page or section; use a button if you're changing information or state"
For example, the "New collection" button creates a new collection *by taking you to the 'Edit collection' page* - I think for a screen reader (for example) styling it as a link makes sense.
From articles like http:// formidablelabs. com/blog/ 2014/05/ 08/anchors- buttons- and-accessibili ty/ and http:// www.karlgroves. com/2013/ 05/14/links- are-not- buttons- neither- are-divs- and-spans/ it looks like the main problem is links which *act* like buttons, regardless of what they look like, so surely buttons which act like links would be just as confusing?